On 15/06/2013 4:08 a.m., [email protected] wrote:
On Friday, June 14, 2013 06:42:41 AM you wrote:
The following configuration works for me:
==================================================
...
...
request_header_access All deny all
request_header_replace User-Agent Mozilla/5.0 (compatible; Goog1ebot/2.1;
+http://www.google.com/bot.html)
request_header_access User-Agent deny all
request_header_access Accept allow all
...
...
request_header_access All deny all
==================================================
OK I don't fully understand your approach, but I started the
request_header_access section like this and it works:
request_header_access Allow allow all
request_header_replace User-Agent Mozilla/5.0 (compatible;
Goog1ebot/2.1; +http://www.google.com/bot.html)
request_header_access User-Agent deny all
...
Putting request_header_replace User-Agent no longer works where it is in the
Squid3 config file. It has to be put further up with the request_header_access
directives.
If that were true it is a bug. The key thing is the existence of these
two lines:
request_header_replace User-Agent ...
request_header_access User-Agent deny ...
You should be able to verify that from "squid -k parse" and the cache
manager "config" report (requires manager password access by default).
I don't understand though, why the config file says "the old http_anonymizer
paranoid" would start with:
request_header_access Allow allow all
?
Because that is just a documentation example detailing which headers the
old obsolete feature "http_anonymizer paranoid" would remove and how to
setup the current header removal feature to behave the same. Since that
old feature existed things have moved on, both in Squid configuration
abilites, HTTP protocol specifications, and Squid support for those
specifications.
Amos
