>Hi
>We have a client who is using Oracle Portal behind a Squid proxy. They are having a problem >whereby documents published via the portal appear to be cached by the proxy, that is, if an >existing document is updated then the new version is often not seen by users who access the >portal via the proxy - they continue to see the old version. Users who bypass the proxy >always see the updated document.
>The steps taken to try and sort the problem are:
>- disable caching on the PC ('always refresh' in the browser)
>- disable caching in the portal
(?)
>- configure the proxy so that it "proxies but no longer caches any data" (the clients words >- I know little about proxies)
>Has anyone any experiences similar to this which they could share with me?
It is the responsibility of the remote webserver(+portal) to provide
correct freshness info , for the discussed items (docs). If it doesn't when
docs are updated then one could state that the remote webserver and
portal architecture is defunct.
Anyway you also have the possibility of limiting a no cache setting in squid.conf
for a particular site/server(see squid.conf). You don't need to disable complete caching
in squid.
M.
Received on Tue Dec 02 2003 - 05:36:45 MST
This archive was generated by hypermail pre-2.1.9 : Thu Jan 01 2004 - 12:00:04 MST