On 28/12/2013 4:12 a.m., Alfredo Rezinovsky wrote: > What squid does in a TPROXY configuration when a client tries to use a > non-http protocol in port 80? > > ToR for example tries port 80. There's a way to squid to seamlessly pass > through the connection when there's not and http conversation? > Squid sends back a 400 status message to the client indicating that its message was not valid HTTP and Squid accepts HTTP/1.1. HTTP supports tunelled connections or data within the HTTP message syntax. ToR and such software are expected to use the appropriate HTTP wrapper messages when using port-80. Amos