Squid代理Header伪造问题：HTTPS网站无法生效求助

问题描述 #

使用Squid代理伪造请求头，在HTTP网站上验证成功，但HTTPS网站上未生效。Squid编译时已启用--enable-http-violations参数，询问配置问题或HTTPS头伪造是否需要额外步骤。

当前squid.conf配置 #

acl localnet src 0.0.0.1-0.255.255.255  # RFC 1122 "this" network (LAN)
acl localnet src 10.0.0.0/8             # RFC 1918 local private network (LAN)
acl localnet src 100.64.0.0/10          # RFC 6598 shared address space (CGN)
acl localnet src 169.254.0.0/16         # RFC 3927 link-local (directly plugged) machines
acl localnet src 172.16.0.0/12          # RFC 1918 local private network (LAN)
acl localnet src 192.168.0.0/16         # RFC 1918 local private network (LAN)
acl localnet src fc00::/7               # RFC 4193 local private network range
acl localnet src fe80::/10              # RFC 4291 link-local (directly plugged) machines

acl SSL_ports port 443
acl Safe_ports port 80          # http
acl Safe_ports port 21          # ftp
acl Safe_ports port 443         # https
acl Safe_ports port 70          # gopher
acl Safe_ports port 210         # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280         # http-mgmt
acl Safe_ports port 488         # gss-http
acl Safe_ports port 591         # filemaker
acl Safe_ports port 777         # multiling ht
#
# Recommended minimum Access Permission configuration:
#
# 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

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# This default configuration only allows localhost requests because a more
# permissive Squid installation could introduce new attack vectors into the
# network by proxying external TCP connections to unprotected services.
http_access allow localhost

# The two deny rules below are unnecessary in this default configuration
# because they are followed by a "deny all" rule. However, they may become
# critically important when you start allowing external requests below them.

# Protect web applications running on the same server as Squid. They often
# assume that only local users can access them at "localhost" ports.
http_access deny to_localhost

# Protect cloud servers that provide local users with sensitive info about
# their server via certain well-known link-local (a.k.a. APIPA) addresses.
http_access deny to_linklocal
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
# For example, to allow access from your local networks, you may uncomment the
# following rule (and/or add rules that match your definition of "local"):
# http_access allow localnet

# And finally deny all other access to this proxy
http_access allow all

# Squid normally listens to port 3128
http_port 3128

# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/cache/squid 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /var/cache/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

request_header_access User-Agent deny all
request_header_replace User-Agent Nutscrape/1.0
connect_timeout 1 minute

问题原因与解决方法 #

核心原因 #

HTTPS请求默认通过CONNECT方法在Squid和目标服务器之间建立加密隧道，Squid仅转发隧道内的加密流量，不会解析或修改其中的请求头——这也是你的配置在HTTP网站生效、HTTPS网站失效的根本原因。--enable-http-violations仅允许修改HTTP协议中非常规的头字段，但无法突破HTTPS隧道的加密限制。

解决步骤 #

1. 启用SSL解密功能
   要修改HTTPS请求头，必须让Squid解密加密流量，这需要配置ssl_bump并生成SSL证书（客户端需信任该证书，否则会出现安全警告）。修改http_port配置并添加ssl_bump规则：

   # 替换原http_port配置，开启ssl_bump并指定证书路径
   http_port 3128 ssl-bump generate-host-certificates=on dynamic_cert_mem_cache_size=4MB cert=/path/to/your/certificate.pem key=/path/to/your/private-key.pem
   # 启用流量拦截与解密
   ssl_bump stare all
   ssl_bump bump all
   

   你可以使用OpenSSL生成自签名证书，示例命令：

   openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout squid-key.pem -out squid-cert.pem
   

2. 确保请求头规则生效
   你的request_header_access和request_header_replace规则已经正确配置，启用ssl_bump后，Squid解密HTTPS流量后会自动应用这些规则修改请求头。

3. 验证配置
   重启Squid服务，配置客户端信任你的自签名证书后，再次访问HTTPS头检测网站即可验证修改是否生效。

内容的提问来源于stack exchange，提问作者Edgar