[squid-users] Clients Header User-Agent replace?
Amos Jeffries
squid3 at treenet.co.nz
Wed Feb 26 05:43:04 UTC 2025
On 25/02/25 23:59, Foxy Lady wrote:
> Hi all.
> Can't figure out how to remove original clients UA from calls.
> Tried out something like,
>
> #USER AGENT
> 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-Enncoding allow all
> header_access Accept-Language allow all
> header_access Content-Language allow all
> header_access Mime-Version allow all
> header_access Cookie allow all
> header_access Set_Cookie allow all
> header_access Retry-After allow all
> header_access Title allow all
> header_access Connection allow all
> header_access Proxy-Connection allow all
FYI, the directive "header_access" is deprecated, typos in the header
names, and you don't have anything forbidden for these rules to re-allow.
In short, those rules appear to be doing nothing.
> request_header_replace User-Agent Mozilla/5.0 (Personal-Test_DevOPS)
> header_replace User-Agent Mozilla/5.0 (Personal-Test_DevOPS)
>
You first have to prevent the clients header from being allowed, then
provide the replacement. Like so;
request_header_access User-Agent deny all
request_header_replace User-Agent Mozilla/5.0 (Personal-Test_DevOPS)
Cheers
Amos
More information about the squid-users
mailing list