Hi, On Mon, Apr 23, 2018 at 4:48 PM, Stephen Nelson-Smith <sanelson@xxxxxxxxx> wrote: > Adding that functionality would be an option, but am I right in > thinking squid should be able to infer the destination from the host > header? > > Just looking at the documentation for http_port, would adding > 'intercept' help, or is that explicitly for interception caching in > conjunction with a traffic filter? Adding `intercept` to `http_port` has resulted in the host header appearing as the URL in the request. Squid is now giving a 403... which it shouldn't... I think: 1524498993.558 0 10.8.0.33 TCP_MISS/403 3985 GET http://www.openstreetmap.com/ - HIER_NONE/- text/html 1524498993.559 0 10.8.2.19 TCP_MISS/403 4077 GET http://www.openstreetmap.com/ - ORIGINAL_DST/10.8.0.33 text/html # Source ACLs acl cluster src 10.8.0.0/16 # Kubernetes Cluster # Destination ACLs acl google dstdomain google.com http_access allow cluster google acl streetmap dstdomain .openstreetmap.com http_access allow cluster streetmap # and finally deny all other access to this proxy http_access deny all S. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
