Welcome to the MacNN Forums.

Parky · Feb 12, 2004, 02:53 AM

Does anyone else have this problem?

I sometimes visit web sites to discover that they have not been updated when I expect them to have been.

I hit the reload button in Safari the page reloads but it is just the same. I hold down the shift key and hit reload, no change.

Even though I know the page has been updated, I can't see the new version.

The only way I can get to see the new page is to open Internet Explorer, go to the page I want to see, hit reload holding down the shift key and the new page appears.

If I then go back to Safari and load the page I will now see the new version.

I realise it must be related to a cache somewhere, but why does IE make the cache renew and Safari does not?

I am using Safari 1.2, and I don't remember having this problem with 1.1, any ideas?

Ian

Moonray · Feb 12, 2004, 03:59 AM

Is there a proxy cacheing web pages?

-

Parky · Feb 12, 2004, 04:10 AM

I have no idea.

Can you explain how I can find out?

Ian

Moonray · Feb 12, 2004, 01:44 PM

Either you have something entered in the Network Preferences, or you are connected through a transparent proxy that is run either by your ISP or local network.

-

Parky · Feb 12, 2004, 01:47 PM

Nothing in Network Preferences.

Must be doing from NTL Broadband.

Ian

geekwagon · Feb 12, 2004, 02:13 PM

Originally posted by Parky:
Nothing in Network Preferences.

Must be doing from NTL Broadband.

Ian

Probably. I have this problem all the time on systems behind a proxy but almost never when I am direct connected.

Safari 1.2 helps somewhat, most of my pages will update now. It was much worse in versions <=1.1.

Most web browsers have a command to signal a "force reload" on the proxy server, but Safari can't seem to do this. You might try to delete your Safari caches.

Lew · Feb 12, 2004, 04:36 PM

The problem is caused by NTL's transparent proxies not updating quickly enough (I'm an NTL customer as well). One workaround you can do is add '?1' (basically a question mark and any number) to the end of the URL which will fool the proxy into thinking you're requesting a new page. I've had this problem when uploading new versions of images to my .Mac webspace and the fix I mentioned seems to make Safari load the new version.

BTW, a good place to get help or have a good gripe about NTL issues is http://forum/nthellworld.co.uk. A lot of NTL's tech support staff post there and you can often get results quicker than via NTL's phone support (although in my experience their broadband phone support is very good)

Love Calm Quiet · Feb 12, 2004, 05:19 PM

Maybe it's just your NTL problem, but...

Have you tried using Safari Enhancer to turn OFF the Safari cache process? It'd be interesting to see if the problem continued after doing so.

Lew · Feb 13, 2004, 02:30 AM

Safari's caches make no difference to this problem as it's to do with NTL's caching proxies. They're just too damned slow at updating (sometimes they can take half an hour to update), so they sometimes show old data. This was told to me by one of NTL's tech support staff.

Parky · Feb 13, 2004, 02:46 AM

It took over 6 hours before NTL had cleared the cache so I could get the latest version of a download!!!

Lew · Feb 13, 2004, 04:54 AM

Did you try the workaround I posted earlier in the thread? I know that it works with inline content but I'm not sure if it'd work with a download.

Parky · Feb 13, 2004, 05:02 AM

It did not work with a download.

Ian

Lew · Feb 13, 2004, 11:10 AM

Bummer. Go and rant at the NTL forum I posted earlier. The more of us customers who complain about NTL's useless proxies the more likely they are to turn them off (IIRC one area has already had its proxies turned off)