Obviously the value I entered is not being passed through.
Connected web sites still see the original user agent string of any used web browser.
On Core Update 146 and reading ipfire’s changelog, I suppose squid is version 4.10.
So, as far as I understand ‘This directive is not available in the 4 version of Squid.’ http://www.squid-cache.org/Doc/config/header_replace/
this feature will not work anymore, despite being available in ipfire’s Web UI.
Is there a workaround for using this feature on Core Update 146?
Perhaps through manual editing squid config?
Obviously the value I entered is not being passed through.
Connected web sites still see the original user agent string of any used web browser.
this is true for HTTPS sites, as IPFire cannot interfere with the content of such traffic.
So, as far as I understand ‘This directive is not available in the 4 version of Squid.’ http://www.squid-cache.org/Doc/config/header_replace/
this feature will not work anymore, despite being available in ipfire’s Web UI.
Thanks for mentioning this - I thought about removing it a while ago, as it does not make sense for most destinations anymore and violates HTTP standards. If Squid dropped it entirely, we should do so as well.
Of course. Should have known that. Kind of embarrassing.
Up to now, I never verified via http connection. To my surprise, despite squid telling otherwise, actually it is still functional. At least http://www.useragent.us displays my proxy fake user agent now.
Sorry, no. I’m content with the way it is now. I was seeking for a method to fake user agent with some smart devices in my home network where I can’t configure webclients. Those are still often connecting to external http servers.
So I would rather leave it as it is for now in addition to fake user agents in webbrowser configurations.
