Thanks for the clue - http cache settings in one of our servers seems to be the problem. FF 5 just started to behave according to standard and that is the point.
Once again - thanks. Lukas -----Original Message----- From: Mark Montague [mailto:[email protected]] Sent: Monday, July 04, 2011 1:10 PM To: Slansky Lukas Cc: [email protected] Subject: Re: [Cosign-discuss] Looping in FF5 (probably) On July 4, 2011 6:22 , Slansky Lukas <[email protected]> wrote: > Since June 22 we're experiencing increased rate of looping in our log files. > Till June 21 we had approximately 0.2 % of looping (over cosign POSTs) but > now it's about 2 %. > > I have investigated our logs and found that this correlates with release of > FF5 and it seems to be valid because FF5 has looping rate about 20 % (!!!). > We have no other updates on our cosign server or other parts of > infrastructure - so FF5 seems to be the problem. > > Has somebody the same experience? Any clues to figure out the real cause? I have not had this experience. However, please use the Live HTTP Headers extension for Firefox 5 to see exactly what is going on when you reproduce the problem: https://addons.mozilla.org/en-US/firefox/addon/live-http-headers/ First, when cosign redirects the user via HTTP 302 responses to requests, does the response include an "Expires" or "Cache-Control" header in addition to the "Location" header? If so, what you are seeing is known behavior for Firefox 5; Firefox 4 and previous apparently handled this differently. Try temporarily disabling Expires headers for the entire web server (central weblogin server and/or the cosign-protected web server, whichever is sending 302 redirects with Expires headers). If this fixes the problem, then you can re-enable Expires headers for those URLs that cosign will not issue redirects for. More information is available at https://bugzilla.mozilla.org/show_bug.cgi?id=667429 If the above is not the cause of the problem, then unless someone else has another suggestion, please include the output of LIve HTTP Headers, showing the full HTTP requests and responses for all of the URLs from when the user first visits the cosign-protected web site through the point at which the looping occurs. This will hopefully provide information as to what is causing the looping. -- Mark Montague [email protected] ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
