Wt

This bug seems to occur from 4.10.0.

If a user reloads a page that is different from the application's base path, this can lead to a series of new sessions being created rapidly. The user is seemingly stuck in an endless loop.
The session tracking doesn't seem to catch that the sessionId belongs to a newly created session, and will invalidate the current session and reload.
It will only do so when a path has been provided that goes deeper than the application's base path.

Likely the changes introduced in #11348 may have introduced this problem.

This can be worked around by not using Combined tracking, but is not a full solution.