I have a page using something along the lines of

<meta http-equiv="refresh" content="0;url=http://example.com/" />

but for certain users on a certain workstation this doesn't work. The is in IE. Is there something wrong with cookies or a setting somewhere which would cause this to fail? I never heard of such a thing.


The problem is that when IE sees this:

<meta http-equiv="refresh" content="0;http://www.example.com" />

it expects the contents attribute to contain a number. The only time IE will check for a URL is if the content attribute contains "URL=" so the redirect that is most usable in all browsers is this:

<meta http-equiv="refresh" content="0;URL=http://www.example.com" />

The above example would redirect immdetiately but if you changed the 0 for another number it would wait that many seconds. Hope this all makes sense, it should work just fine but I still think my first idea was the better one.


There is a security setting in internet explorer that does not allow meta tag refresh. It is under the Security tab, then choose Custom Level and the Meta Tag Refresh under Miscellaneous. If that is disabled, it would stop the meta refresh from working.

Aside from being able to disable it selectively, it is automatically disabled if you set IE's security level to 'High' [observed in IE9].


is it a really old version of IE? if so, try:

<meta http-equiv="refresh" content="0;url=http://example.com/"> </meta>

It needs a white space. HTML editor will complain, but just ignore it.