Migrated content claims to be 301ed but I can view it in Safari

[Andiamo]

A client just redesigned their site and claims to have 301-ed the entire site to relevant URLs on the new site. The issue is that although a header check reveals that pages on the old site have, in fact, been 301-redirected, I can still view the content on the old site, on the old site's URLs.

This is only the case in Safari - in Chrome and Firefox, the site redirects. Any idea why that would be?

[brotherhood of LAN]

A caching issue perhaps.

If the HTTP headers are indeed correct then the redirect should work as intended.

Try using a command line client like wget or cURL to ensure it's not just a browser cache.

If the redirect is there + content, then it's more of a coding issue on your old domain.

[lucy24]

Before anything else: Clear the browser's cache. It's even better if you can test on an entirely different copy of the same browser. "Clear your cache" is the webmaster's equivalent to "Is the appliance plugged in?"

As a further complication: 301 responses may themselves be cached by the browser. So if you change a redirect target and then type in the original URL, the browser might still send you to the earlier target. A forced refresh should set you right.

And then there's remote caching by your ISP, and possibly other points along the way...

[paulsimmons]

This the cache issue.. Try refreshing your browsers cache. similar issue happened on Firefox for me when I redirected to the new URL but it wasn't redirecting at all.