On 03/16/2017 07:37 PM, 钱国正 wrote: > acl subnet src 192.168.0.0/16 > on_unsupported_protocol tunnel subnet
The on_unsupported_protocol directive does not (and cannot) work for cases where Squid does not know where the client is trying to get to: > Currently, this directive has effect on intercepted connections and > bumped tunnels only. Other cases are not supported because Squid > cannot know the intended destination of other traffic. AFAICT from your logs, Squid was not bumping a CONNECT tunnel. Did Squid intercept the connection with a non-HTTP request? What is your http_port 3128 configuration in squid.conf? And if your Squid is not intercepting (i.e., it works as a regular HTTP forward proxy), then why is it receiving non-HTTP requests and what would you like Squid to do with them? Alex. > 2017/03/16 17:36:46.496| 5,2| TcpAcceptor.cc(315) acceptNext: connection on > local=[::]:3128 remote=[::] FD 15 flags=41 > 2017/03/16 17:36:46.499| 33,2| Http1Server.cc(101) buildHttpRequest: Invalid > Request > 2017/03/16 17:36:46.499| 4,2| errorpage.cc(1260) BuildContent: No existing > error page language negotiated for ERR_PROTOCOL_UNKNOWN. _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
