On 8/10/19 2:17 pm, johnr wrote:
> The rest of my config is the same between squid 3 and squid 4. I have an
> ICAP reqmod that modifies the request user-agent. In squid 3, the value is
> the properly modified value. In squid 4, the value is the original UA.
> According to the transaction processing
My config is as follows:
Squid 3:
external_acl_type should_not_ssl_bump ipv4 ttl=10 %DST %>{User-Agent}
/etc/should_not_ssl_bump.py
acl should_not_ssl external should_not_ssl_bump
ssl_bump none should_not_ssl
Squid 4:
external_acl_type should_not_ssl_bump ipv4 ttl=10 children-startup=1
childre
On 2019-10-08 12:15, johnr wrote:
In squid 3.5, passing a request header into the external ACL was post
reqmod
(if I added a header in ICAP, it was available in the external ACL).
Not quite. It depended on when the ACL was tested: pre or pos-
adaptation. Obviously testing the ACL in http_acce
In squid 3.5, passing a request header into the external ACL was post reqmod
(if I added a header in ICAP, it was available in the external ACL). In
squid 4, this doesn't seem to be the case. Is that intentional?
Further, the logformat codes that the external ACL now supports should allow
access t
