HTTP CONNECT

El método CONNECT convierte un proxy HTTP ordinario en un túnel ciego. Un cliente envía CONNECT host:443 al proxy; el proxy abre una conexión TCP a ese host y, una vez establecida, simplemente reenvía bytes en ambas direcciones sin interpretarlos. Esto es lo que permite que un proxy HTTP autenticado transporte HTTPS: el proxy solo ve el host y el puerto de destino, nunca el contenido cifrado, porque el apretón de manos TLS ocurre de extremo a extremo entre el cliente y el servidor real a través del túnel.

The s4m HTTP proxy at proxy.s4m.online:3128 uses CONNECT to carry your HTTPS traffic. You supply USER:PASS credentials (see proxy authentication), and the proxy tunnels the encrypted session to your target. Because the proxy cannot read tunnelled TLS, your confidentiality is whatever the end-to-end HTTPS already provides. If you need to relay non-HTTP protocols too, the SOCKS5 endpoint on port 1080 is lower-level and more flexible, whereas CONNECT is specific to the HTTP-proxy world and web traffic.

When configuring a client, point HTTPS traffic at proxy.s4m.online:3128 with your USER:PASS and the library issues CONNECT for you automatically. If you also need to relay non-HTTP protocols or UDP-based ones, reach for the SOCKS5 endpoint on port 1080 instead, since CONNECT is specific to web traffic. Because the tunnel is opaque, your privacy through it is whatever end-to-end TLS already provides — the proxy adds a hop and an exit IP, not extra encryption.