HTTP Proxy: Forward Requests and CONNECT Tunnels
A forward HTTP proxy is an intermediary selected by a client. It receives the client’s request and makes or relays an upstream request according to its configuration and policy.
Updated · Editorial approach and simulation limits
A forward proxy acts on behalf of the client
A browser configured with an HTTP proxy connects to that proxy rather than directly to the origin server. For ordinary HTTP requests, the proxy receives the target authority, applies local policy and forwards a request upstream. The browser then reads the response through the proxy.
The proxy can authenticate the client, log selected metadata, cache eligible responses or block destinations. These behaviors depend on configuration and HTTP semantics; the term proxy does not imply that the intermediary decrypts every connection.
CONNECT creates a tunnel for HTTPS
For HTTPS, a client commonly sends CONNECT with the target host and port. If the proxy permits the request, it establishes a tunnel and returns a success response; the client can then perform TLS through that tunnel to the origin. The proxy sees connection metadata but, without a separate trusted interception arrangement, TLS protects the application content from it.
A CONNECT failure is an HTTP proxy response, not a TLS certificate error. If CONNECT succeeds but the TLS handshake fails, examine certificate validation, name resolution, the origin and the path through the tunnel separately.
Separate proxy, origin and transport failures
In a trace, identify which connection is between the client and proxy and which is between the proxy and origin. A client may see one socket while the proxy opens another. Compare request target form, proxy authentication, response status and tunnel setup before blaming the origin server.
An HTTP proxy handles HTTP semantics. SOCKS5 is a more general proxy negotiation protocol, while a reverse proxy sits in front of servers and receives inbound traffic. These roles can coexist but are not interchangeable.
Explore HTTP Proxy interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 9110: HTTP Semantics. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all application protocols · Compare HTTP/2 and HTTP/3 transport paths