[squid-users] debug_options appears to change squid behaviour

Mark Carey mark.carey at gmail.com
Mon May 9 05:19:34 UTC 2016


Running squid 3.1.19-1ubuntu3.12.04.2.

acl sefup dst massing-uploads.s3.amazonaws.com
acl sefairauser src
http_access allow sefairauser sefup
http_access allow CONNECT sefairauser sefup

When run "normally" and my application (or browser) tries to access
the site I get, TCP_DENIED

1462769200.720      6 TCP_DENIED/403 3737 CONNECT
massing-uploads.s3.amazonaws.com:443 - NONE/- text/html

If I enable debugging

debug_options 28,1

The application seems to start working

1462769557.248  10409 TCP_MISS/200 4026 CONNECT
massing-uploads.s3.amazonaws.com:443 - DIRECT/ -

Now the server owner could be having problems at their end and dishing
out different responses from different hosts in their pool of hosts in
their Amazon AWS cloud.

Is there any reason why squid would use different code paths with
debug_options set?

Thank you.

Mark Carey

More information about the squid-users mailing list