There is a bug in the SSL-Bump implementation we have not sorted out
yet, which makes the "ssl-bump" on this port enable reverse-proxy mode
handling. That seems to be leading to Surrogate feature being enabled
and the Authorization:Bearer being removed when it should be relayed to
the server.
Here is the snippet of debug logs
I dont get to see anything missing out there . It does a GET call to the
docker registry on behalf of the requesting client The registry listens on
443 so squid mimicks client TLS connections post which does a GET call to
the docker registry on the requested
Team -
Would like to know is there any specific config that we need to enable to
cache MIME attachement of application/octet-stream type
We are trying to caching docker image blobs which is of
application/octet-stream and everytime we hit the docker registry via)GET
call squid throws up
