-
Notifications
You must be signed in to change notification settings - Fork 25
Increase Infinite Redirect Protection (MWF 1.2) #135
Comments
Heh. Last night, I was trying to write a test for the fix you already did. I stumbled on this issue and have been working on devising a real-world situation where it is tripped. I think a transparent proxy that disallows cookies will trip it, but I don't know how common that is. (Installing squid right now to see if I can trip it.) |
Let me know if you can trigger the issue. If I just had one of those Blackberry's that have been causing us so many problems, I suspect it would be as easy as querying the URL ;) |
The proposed solution is in. This simply extends the solution for the known issue with passthru.php by doing a reload with |
Reopening because there's a bug in this. |
Merged the portion that didn't carry over from my fix to UCLA Mobile. |
Here's how to trigger. This is a crazy edge case, I'm sure. But killing one crazy edge case we know about probably kills a dozen others we haven't even thought of.
I have a Cucumber test that I can commit that more-or-less does this in PHP and JS code without squid. Will commit shortly. |
Does this solve the issue? Make sure to pull both commits since the first was partial only. On Apr 15, 2012, at 10:41 AM, "Trott" reply@reply.github.com wrote:
|
While
passthru.php
was patched in MWF 1.2.14 and is ready for MWF 1.3 (see #133), we extended the fix slightly at UCLA. The reason is that, in addition topassthru.php
, there's also reload logic inserver.js
. The addition that can be made is as follows:Formerly:
The fix::
The text was updated successfully, but these errors were encountered: