RE: [squid-users] Problem with HTTP Header UserAgent

Thanks Henrik!

I'm not familiar with Squid at all, but I did find the following excerpt of
information that sounds exactly like what you are talking about:

Tag Name: anonymize_headers
 
Usage: anonymize_headers allow|deny header_name ...

Description:
This option replaces the old 'http_anonymizer' option with something that is
much more configurable. You may now specify exactly which headers are to be
allowed, or which are to be removed from outgoing requests.
There are two methods of using this option. You may either allow specific
headers (thus denying all others), or you may deny specific headers (thus
allowing all others).

For example, to achieve the same behavior as the old 'http_anonymizer
standard' option, you should use:
anonymize_headers deny From Referer Server
anonymize_headers deny User-Agent WWW-Authenticate Link

Am I correct in guessing that this is the setting that needs to be changed
to enable the User-Agent HTTP header?

Thanks for your help,
Bob

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Wednesday, May 29, 2002 3:25 PM
To: Bob Whitley
Cc: 'squid-users@squid-cache.org'
Subject: Re: [squid-users] Problem with HTTP Header UserAgent

Bob Whitley wrote:
>
> Has anyone encountered a problem with Squid 2.4 and IE where the HTTP
Header
> "UserAgent" has a value of "Unknown/1.0" when it should be something like
> "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)"?

Only if you are using the anonymization features of Squid to filter away
the User-agent string..

Meaning, if you tell Squid not to tell servers which browser you are
using, then it won't. This filtering to anonymize the user is not
enabled by default, but can be enabled in squid.conf.

Regards
Henrik
Received on Wed May 29 2002 - 17:19:24 MDT