Alex Rousskov wrote > Thus, the existing implementation should cover non-HTTP > requests on port 80 (or 3128). If it does not, it is a bug. We should > polish the documentation to make this clear. The problem is not squid itself . The problem is in some situations for example DOS(with malformed requests) , infected clients sends lots of requests to target server . The requests goes through squid tproxy so squid will send back about 250 byte in reply to each request . So i am looking for a way to just send tcp reset and not that 250 bytes . HTTP/1.1 403 Forbidden Server: squid Mime-Version: 1.0 Date: Wed, 24 Aug 2016 14:11:35 GMT Content-Type: text/html;charset=utf-8 Content-Length: 5 X-Cache: MISS from cache1 X-Cache-Lookup: NONE from cache1:3128 Connection: close -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-RESET-non-http-requests-on-port-80-tp4679102p4679147.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
