Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
None
Description
On occasion it is possible to construct series of redirects that would result in the infinite loop. E.g. Redirect from uri A forwarding to B and existing redirect from B redirecting back to A in simplest case or in more complicated example uri A forwarding to B, B forwarding to C and C forwarding back to A.
Magnolia should detect such loops and if occurring break them down.
Please note multiple possible mechanisms of such redirects working. Apart from possibility of regexp being used in "fromURI" parameters, there's also possible combination of includes, forwards and permanent redirects some of which result in triggering from browser thus make detection more difficult (e.g. browser callback can reach another public instance in multi-instance load-balanced setup).
Without implying what solution should be, some means of tracking the fact that call is a redirect as part of the link when browser is involved will most likely be necessary.
Checklists
Attachments
Issue Links
- Wiki Page
-
Wiki Page Loading...