HTTP proxy
A proxy that understands the HTTP protocol and forwards web requests, optionally reading and modifying headers along the way.
An HTTP proxy is specialised where a SOCKS5 proxy is indifferent. It speaks the protocol your browser speaks, so it does not just move bytes: it parses the request line and the headers, and can therefore cache a response, route on what it sees, rewrite a header, or refuse a request on content grounds. Understanding the traffic is the entire point of it.
That understanding is also the origin of its most quoted drawback. Because it handles the request as HTTP, it can add headers describing where the request came from, which is precisely what the anonymity grades measure: an anonymous proxy strips your address from those headers but leaves a trace of itself, and an elite proxy adds nothing at all. A SOCKS proxy never faces that question, because it was never going to write an HTTP header in the first place.
For encrypted destinations it deliberately steps back. When you request an HTTPS page, the client issues a CONNECT and the proxy opens a blind tunnel, passing the encrypted stream through without reading it, because it cannot look inside TLS without breaking the encryption. So an HTTP proxy carries HTTPS perfectly well and simply loses its inspection and caching abilities while doing so. This is also why the labels HTTP proxy and HTTPS proxy usually describe the same endpoint rather than two products.
Which sets the practical boundary against SOCKS5. If your traffic is web requests, an HTTP proxy is the natural fit and the one almost every tool supports without configuration. If your traffic is anything else, email, a database connection, a game protocol, or anything needing UDP, it cannot help you, because it only knows one protocol and yours is not it.
One deployment note worth having: this term normally means a FORWARD proxy, something you configure and send your traffic through. A reverse proxy also speaks HTTP and sits at the other end, in front of somebody's servers, working on the site's behalf rather than yours. Same protocol, opposite direction, and the two get confused constantly.
Frequently asked questions
What is the difference between an HTTP proxy and an HTTPS proxy?
Usually nothing, despite the two labels. The same endpoint handles both: it processes plain HTTP requests directly, and for HTTPS it opens a tunnel with CONNECT and passes the encrypted stream through untouched. A provider listing HTTP and HTTPS is almost always describing one proxy that does both, not two different products.
HTTP proxy or SOCKS5, which should I use?
If you are moving web traffic, an HTTP proxy is the simpler answer and is supported by essentially every tool without special configuration. Choose SOCKS5 when you need anything that is not HTTP, when you need UDP, or when you want the proxy to resolve hostnames on your behalf so your own DNS server never sees the destination.
Can an HTTP proxy see my HTTPS traffic?
Not the contents. Once CONNECT opens the tunnel the operator relays encrypted bytes it cannot read. It still sees the destination hostname you asked to reach, the timing and the volume of traffic, which is meaningful metadata even without the payload. The exception is an intercepting setup that installs its own certificate on your machine, which is how corporate inspection works and which you would have had to permit.
Does an HTTP proxy leak my real IP?
That depends entirely on its anonymity grade, and it is the one proxy type where the question arises. A transparent proxy passes your address straight through in the headers. An anonymous one removes your address but still announces that a proxy is involved. An elite one adds no such headers at all. The only way to know which you have is to send a request and read back the headers that arrived.
Back to the full glossary.