[squid-users] connect with http and https protocols

Matus UHLAR - fantomas uhlar at fantomas.sk
Wed Apr 30 13:47:11 UTC 2025


On 30.04.25 14:39, Renzo Marengo wrote:
>what you are saying It's very interesting, infact previously I understood
>CONNECT method was invoked both by http and by https protocols.
>You are saying CONNECT method is invoked only if protocol is https, while
>if you type http://site:port, no CONNECT method is invoked.
>Right ?

Correct.

While it is possible to issue CONNECT for HTTP request, most clients do not 
do that, and squid does not allow by default CONNECT requests to port 80 
(where most HTTP servers listen at).
The FTP requests are often also issued through GET/PUT requests instead of 
CONNECT, the default FTP port 21 is also not allowed by default.

Also, using GET requests gives us advantage to cache content on proxy's 
side, which may benefit us in lower latency and spared bandwidth.

There's still much of internet content that is available without encryption, 
like CRL lists or any kinds of signed content, where you don't have to be 
afraid of it being modified, e.g. debian packages


-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I just got lost in thought. It was unfamiliar territory.


More information about the squid-users mailing list