[squid-users] header_replace User-Agent for SSL connections?

From: WEHT.net Webmaster <webmaster@dont-contact.us>
Date: Wed, 22 Oct 2003 21:05:52 -0400 (EDT)

Thanks to all for the replies on my SSL Tunnel question (it would
be nice if there was a way to use PAC to tell the client to use
SSL to connect...)

At any rate, still under 2.5.STABLE4

header_replace User-Agent Nutscrape 1.0

works fine only for http connections, when you go through the squid
proxy for an https:// url (SSL) the original user agent shows up
in the logs.

I imagine there is either a good reason for this or some configuration
option I'm overlooking.

Is there a way to set this for SSL? (Basically anonymizing headers
as follows):

header_access Allow allow all
header_access Authorization allow all
header_access Cache-Control allow all
header_access Content-Encoding allow all
header_access Content-Length allow all
header_access Content-Type allow all
header_access Date allow all
header_access Expires allow all
header_access Host allow all
header_access If-Modified-Since allow all
header_access Last-Modified allow all
header_access Location allow all
header_access Pragma allow all
header_access Accept allow all
header_access Accept-Encoding allow all
header_access Accept-Language allow all
header_access Content-Language allow all
header_access Mime-Version allow all
header_access Retry-After allow all
header_access Title allow all
header_access Connection allow all
header_access Proxy-Connection allow all

header_access User-Agent deny all
header_replace User-Agent Nutscrape 1.0

I also notice that fake_user_agent and anonymize_headers seems to
have depreciated out of 2.5 ?

Thanks, mark

-- 
WEHT.net
The Online Compendium of "What Ever Happened To" & "Where Are They Now?"
Subscribe to the newsletter at http://WEHT.net/newsletter.php
Received on Wed Oct 22 2003 - 19:05:55 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:20:36 MST