RE: [squid-users] Oracle Portal

Thanks for that.

I think the client has just disabled caching for the relevant server.

I would agree that in an ideal setup, the webserver should be responsible for maintaining 'freshness'. I suspect that there is a configuration gotcha with Portal and Squid which is causing this problem, I am hoping someone else has hit this.

Manfred

-----Original Message-----
From: Elsen Marc [mailto:elsen@imec.be]
Sent: 02 December 2003 12:37
To: Manfred Milhofer; squid-users@squid-cache.org
Subject: RE: [squid-users] Oracle Portal

>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.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003
 
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003