Protocols
Saved & recent

HTTP CONNECT

Also called: CONNECT method, HTTP tunnel

CONNECT asks a proxy to establish a tunnel to a destination. In the classic HTTP/1.1 form, the target is a host and port. After a successful response, the proxy forwards bytes in both directions rather than interpreting them as ordinary HTTP request bodies. The tunnel itself does not provide encryption.

For example, a client sends CONNECT archive.example:443 to its proxy. Once the proxy confirms the tunnel, the client can perform TLS with the archive server through it, keeping that TLS connection’s endpoints at the client and archive. Proxy policy still controls which destinations are allowed. Extended CONNECT mechanisms for newer HTTP versions have additional, separately specified rules.

Read first
HTTP
Related
Web proxy, TLS, HTTPS
Further reading
IETF RFC 9110 — CONNECT
client proxy archive server CONNECT archive.example:443 successful 2xx response HTTP/1.1 setup proxy forwards bytes end-to-end TLS TLS client TLS archive server byte tunnel after setup
Classic HTTP/1.1 CONNECT first creates a byte tunnel. The client can then negotiate TLS through it with the archive server; this forwarding proxy is not a TLS endpoint, and the tunnel alone is not encryption.

View in the full Protocols collection