[squid-users] Entries are cached on the result of the URL rewriting process?

2007-07-28 Thread Ricardo Newbery
In the default squid.conf, this warning confuses me: # TAG: url_rewrite_host_header # By default Squid rewrites any Host: header in redirected # requests. If you are running an accelerator this may # not be a wanted effect of a redirector. # # WARNING: Entries are cache

Re: [squid-users] Entries are cached on the result of the URL rewriting process?

2007-07-29 Thread Michael Pye
Ricardo Newbery wrote: > I'm pretty sure entries are cached (and are purgeable) based on the URL > coming into squid, not whatever squid rewrites it to. No - they are cached as it states based on what URLs are rewritten to. You have to be careful in reverse proxy setups if you are attempting to r

Re: [squid-users] Entries are cached on the result of the URL rewriting process?

2007-07-30 Thread Ricardo Newbery
On Jul 29, 2007, at 3:02 PM, Michael Pye wrote: Ricardo Newbery wrote: I'm pretty sure entries are cached (and are purgeable) based on the URL coming into squid, not whatever squid rewrites it to. No - they are cached as it states based on what URLs are rewritten to. You have to be carefu

Re: [squid-users] Entries are cached on the result of the URL rewriting process?

2007-07-30 Thread Henrik Nordstrom
On mån, 2007-07-30 at 01:24 -0700, Ricardo Newbery wrote: > Purges work with the incoming url. Purges don't work with the > outgoing url (or actually, the outgoing *path* fed into the squid > host:port). purge requests is also subject to the url_rewriter before they are processed. Regards H