Safari caching problem

Question

Level 1

0 points

Safari caching problem

Hi,

I wonder if any of you can help? Normally safari caching a page isn't a problem. I like that it stores little bits of the page away for quick reloading! I just hit reload and up comes the new webpage. Failing that I empty the cache under the file menu or reset safari under the same menu.

Only this time that's not working. I surf on over to my site to be greeted by a page I actually ftp-deleted two days ago! I've checked that it's not a server issue. I've had a quick look around the web and can't seem to find anything. It's the latest version of the browser running on a power mac g5.

Thanks,

Ben

Power Mac G5 Mac OS X (10.4.6)

Posted on May 24, 2006 8:54 AM

Reply

Answer 1

daveyh

Level 1

40 points

May 24, 2006 9:34 AM in response to Ben Goodson

Have you tried another machine or another browser? If another browser or machine on the same network is also showing the old pages, it could be that your ISP is caching pages. You can check via a proxy site like www.proxify.com to see whether the site actually loads correctly from outside your network.

Reply

Answer 2

Ben Goodson Author

Level 1

0 points

May 24, 2006 9:44 AM in response to Ben Goodson

Thanks David,

I headed over to proxify and it displays the latest version of the page as I would expect to see it. However...okay that's weird. I've just been to the site again through safari and everything loads up correctly. No old pages!

Now why would that be? It's been showing me a cached page for over twelve hours. Why would my ISP be caching pages? Or more specifically, only my webpage (every other site on the net seeminly works fine).

Thanks again, looks like problem temporarily resolved.

Reply

Answer 3

daveyh

Level 1

40 points

May 24, 2006 10:03 AM in response to Ben Goodson

I wish I had a definitive answer but this has happened to me numerous times when updating my own sites. It seems to be something that is related specifically to Safari. I can only guess that it might possibly be the type of request that is being sent to the server?

Reply