up vote 0 down vote favorite
share [g+] share [fb]

We have a bug in a library which is used in a ton of web applications. The bug is that it redirects the user to a login page using 302 permanently moved instead of temporary moved. This causes Firefox 5 (and possibly later) to cache the response and redirect the user everytime he tries to access the page.

I have looked into about:config properties, but cannot find anything worth tuning.

I've looked into the property: network.http.redirection-limit;20 , but I dont think this is the correct value to change.

link|improve this question
100% accept rate
1  
I once had a bug like this in an HTTP server. I took the route of fixing the bug, and kicking myself for such a mistake, rather than breaking the protocol. Breaking protocol to accommodate bugs is a cause of problems, not a solution for them. Gresham's Law trumps Postel's Principle. – JdeBP Oct 12 '11 at 11:48
You need to fix the library instead of trying to break standardized behaviour in the browser. – ThiefMaster May 11 at 7:25
feedback

1 Answer

up vote 1 down vote accepted

This question does not apply to me anymore. We had to take the pain and fix the library. All in all this was the healthiest solution!

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.