Team -
Would like to know is there any specific config that we need to enable to cache MIME attachement of application/octet-stream type ====
1475056789.667 0 10.0.0.160 TAG_NONE/200 0 CONNECT <docker registry>:443 - HIER_NONE/- -
1475056789.706 1633 10.0.0.160 TCP_MISS/200 1114 GET https://docker registry/v2/blobs/sha256:36e0da2b6e166c5e7b1f243e9257590d4fbd1be729773df7f3d6a779941b22d9 - FIRSTUP_PARENT/IP.xx.xx.xxapplication/octet-stream
1475056789.708 0 10.0.0.160 TAG_NONE/200 0 CONNECT <docker registry>443 - HIER_NONE/- -
1475056791.259 1545 10.0.0.160 TCP_MISS/200 1698 GET https://docker registry/v2/blobs/sha256:2a00f8fcea92b16de0de328c557da476e930aa038ccee482daf91a62de5afa33 - FIRSTUP_PARENT/IP.xx.xx.xx application/octet-stream
=============
http_port docker registry:443 ssl-bump cert=/etc/ssl/private/docker registry.certkey=/etc/ssl/private/docker registry.key
maximum_object_size 8 GB
maximum_object_size_in_memory 102400 KB
quick_abort_min -1
cache_dir ufs /data/squid/cache/squid 204800 16 256
cache_mem 51200 MB
cache allow all
cache_peer docker registry parent 443 0 no-query originserver no-digest name=upstream ssl sslflags=DONT_VERIFY_PEER
never_direct allow all
#
acl site dstdomain /etc/mirror-dstdomain.acl
acl site1 dstdomain docker-registry.xx.xx
http_access allow site
http_access allow site1
cache_peer_access upstream allow site1
cache_peer_access upstream deny all
ssl_bump bump site1
ssl_bump splice all
sslproxy_flags DONT_VERIFY_PEER
_____________________________________________________________
The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt._______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users