User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a3) Gecko/20100315 MozillaDeveloperPreview/3.7a3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a3) Gecko/20100315 MozillaDeveloperPreview/3.7a3 This Web-site stopped to load when i update my Firefox Web-browser from version 3.5.x up to 3.6.x. In version 3.7a3 this bug is not resolved too :( I tried to turn off all my plug-ins and to modify param "network.http.redirection-limit" in "about:config", but this don't help. In browsers IE 8, Google Chrome and Opera it seems to be all OK... P.S. Sorry for my bad English... Reproducible: Always Steps to Reproduce: 1. Try to load this page(uva.onlinejudge.org) in Mozilla Firefox >= 3.6.x Actual Results: The page isn't redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never complete. This problem can sometimes be caused by disabling or refusing to accept cookies. Expected Results: Load this Web site, not throw this exception...
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a4pre) Gecko/20100330 Minefield/3.7a4pre This works fine for me. Also Firefox 3.6 loads the page.
Have you any plugins installed on FF 3.6?
Works fine with FF 3.6.3 here too.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.