You could tell the complaining customers to configure their browser to use the proxy as a solution to the problem.
Regards Henrik On Thursday 20 February 2003 21.58, Valentin Chopov wrote: > Henrik, > > thanks for the suggestion. Unfortunately not using WCCP is not an > option for us;) I don't know if you mean "ie_refresh" option but > it's tutned on in our case. Is there something else what we can do? > > Thanks again, > > Val > > On Thu, 20 Feb 2003, Henrik Nordstrom wrote: > > Don't use interception (including WCCP). > > > > Using interception hides the fact that you are using a proxy > > cache from the browsers, so the browsers do not know they need to > > include cache instructions to instruct caches to fetch a fresh > > copy when the user pushes the reload button.. > > > > Configure the browser to use a proxy and things should work much > > better. > > > > > > There is also some (one) options in squid.conf which may help.. > > > > Regards > > Henrik > > > > On Thursday 20 February 2003 19.48, Valentin Chopov wrote: > > > Hi, > > > > > > It seems I have a problem with FrontPage sites cacheing. > > > I got complaints that after making changes to their web > > > pages (which are hosted on the servers outside our network) > > > the updates can not be seen behind our squid proxy servers, > > > even after hitting refresh on the browser. > > > I think the most of complains are about FrontPage web sites but > > > I didn't check all of them. > > > We are running Squid 2.5 + WCCP. Currently I'm fixing this > > > with ACLs on the Cisco routers to exclude the IPs from the > > > WCCP. Is there a way to fix this globally? > > > > > > Thanks, > > > > > > Val > > > > > > == > > > Valentin S. Chopov, CCNP > > > Sys/Net Admin > > > SEI Data Inc. > > > E-Mail: [EMAIL PROTECTED] > > > ==
