visible_hostname *********
#
# Recommended minimum configuration:
#
acl manager proto cache_object
acl localhost src ********.0.1/** ::1
acl to_localhost dst **********.0.0/8 0.0.0.0/32 ::1
# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src ***.*****.0/12 # RFC1918 possible internal network
acl localnet src ****.*******0.0/16 # RFC1918 possible internal network
acl localnet src ******::/7 # RFC 4193 local private network range
acl localnet src ******::/10 # RFC 4291 link-local (directly plugged) machines
******************************
acl SSL_ports port 4*
acl Safe_ports port 8* # http
acl Safe_ports port 2* # ftp
acl Safe_ports port 4* # https
acl Safe_ports port 7* # gopher
acl Safe_ports port 2* # wais
acl Safe_ports port 1* # unregistered ports
acl Safe_ports port 2* # http-mgmt
acl Safe_ports port 4* # gss-http
acl Safe_ports port 5* # filemaker
acl Safe_ports port 7* # multiling http
acl CONNECT method CONNECT
no_cache deny all
#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager
# Deny requests to certain unsafe ports
http_access deny !Safe_ports
# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports
# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost
# And finally deny all other access to this proxy
#http_access deny all
****************************
# Squid normally listens to port ****
http_port ***
# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/spool/squid 100 16 256
#otkluchit cash
#cache deny all
# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid
# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320
Не знаю. Но если ты хотел сказать, что Squid не может кешировать https трафик, то таки да, не может. Без man-in-the-middle он просто не может определить, что за ресурсы качаются.
Некоторые провайдеры применяют такие системы DPI, которые умеют перехватывать запросы даже внутри прокси-сервера, на любом порту. Помогает шифрование прокси-сервера (опция https_port в squid). Работает только в браузерах, основанных на Firefox/Chromium, через PAC-файл (в обычных настройках такие прокси нельзя указать), и в некоторых программах (curl).