Hi Henrik, I want to try and achieve this setup so that content is returned to clients as fast as possible, but also trying to make sure that my infrastructure is queried for it every time someone tries to access it, even if it's just for logging purposes. Would the combination of header_access/header_replace be a suitable way to achieve this? Cheers Joe Joe Tiedeman Support Analyst Higher Education Statistics Agency (HESA) 95 Promenade, Cheltenham, Gloucestershire GL50 1HZ T 01242 211167 F 01242 211122 W www.hesa.ac.uk -----Original Message----- From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Monday 18 August 2008 01:13 To: Joe Tiedeman Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: caching headers sön 2008-08-17 klockan 21:35 +0100 skrev Joe Tiedeman: > > I am currently used squid as a caching reverse proxy. I would like to > know if it's possible to have the web server return the appropriate > caching headers to squid and have squid rewrite/replace the headers to > make the client not cache the responses. Why? Most want's to do the opposite... aggressively cache in the clients and less aggressively cache in the reverse proxy.. Regards Henrik ______________________________________________________________ This incoming email was virus scanned for HESA by MessageLabs. ______________________________________________________________ _____________________________________________________________________ Higher Education Statistics Agency Ltd (HESA) is a company limited by guarantee, registered in England at 95 Promenade Cheltenham GL50 1HZ. Registered No. 2766993. The members are Universities UK and GuildHE. Registered Charity No. 1039709. Certified to ISO 9001 and BS 7799. HESA Services Ltd (HSL) is a wholly owned subsidiary of HESA, registered in England at the same address. Registered No. 3109219. _____________________________________________________________________ This outgoing email was virus scanned for HESA by MessageLabs. _____________________________________________________________________
