Closed Bug 374444 Opened 19 years ago Closed 19 years ago

refresh meta stopped working

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: bugzilla.mozilla.org, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2 Not sure this started with version 2.0.0.2, happens only on some machines, but is always reproducible. refresh meta stopped to work. For instance <meta http-equiv="refresh" content="0;URL=targetPage.html"> does not have any result. For instance, going to http://microsoft.com/vista doesn't work at first. If you hit the refresh button, then, it works and continue to do so on subsequent visits. I don't know how to narrow the field of search but I'm willing to help. Reproducible: Always Steps to Reproduce: 1. 2. 3.
The link you mention uses HTTP redirects rather than meta redirects to move you to the real page of http://www.microsoft.com/windows/products/windowsvista/default.mspx So is this bug about meta refreshes or http redirects?
(In reply to comment #1) > The link you mention uses HTTP redirects rather than meta redirects Rather a poor choice of test case, I must admit. I should have investigated further. Obviously a web farm cascading many tricks to manage its traffic. I was stuck there several times on the barest page containing only a very quick meta refresh of its own URL. Now for a better test case: http://acmenta.net/mozilla/refreshTest.html This page should take you to http://acmenta.net/mozilla/refreshTarget.html But it doesn't work for me. HTH
works for me in recent bonecho 2.0.0.3 on winxp/linux. You don't have an extension or pref that is blocking the refresh are you?
(In reply to comment #3) > You don't have an extension or pref that is blocking > the refresh are you? That's the first thing I thought of. But why would several computer have the same extension with this same setting enabled pretty much at the same time? Can't be. I should have checked anyway, as you are right: they had the Web Developer add on with Disable Meta Redirect enabled. As simple as that. Just the old me busy making a fool of itself... Duh... Thanks for everybody help and sorry for the time lost.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
works for me would have been a better resolution but invalid works for me too. :-) If this is the worst misteak you make, then you are doing fine. thanks for the bug report.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.