Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Can any one please explain what does the reply_header_access configuration directive does? (and yes, I have RTFM, but I still do not understand what it does.)

share|improve this question
up vote 1 down vote accepted

This directive allows squid to remove headers from the HTTP reply before returning it to the client. You might do this because you're using Squid as a reverse-proxy and you want to "anonymize" your web servers (removing the "Server" header, for example) or to hide the presence of the cache (removing headers like "Via", "X-Cache", etc, for example).

There is a "request_header_access" directive to do the same things to the client's request headers.

Both directives apply based on ACLs such that you can be very flexible in determine to which requests the directives will actually apply.

share|improve this answer
thanks for the answer. I have two more questions that may know the answer to: 1) can I send a different header value instead of just having squid remove the header? 2) can i do this for the Cache-Control header as well? – Nir Levy Dec 2 '09 at 13:57
This entry in the Squid FAQ should be helpful: You can manipulate the cache-control header. – Evan Anderson Dec 2 '09 at 18:38
Found out that using ACL "it is not possible to replace a response header because the header_replace option only works with HTTP requests". Thanks again for the help and pointers. – Nir Levy Dec 3 '09 at 10:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.