Two modes#
| Mode | How it works | What the proxy sees |
|---|---|---|
| Plain HTTP | The client sends GET http://example.com/path to the proxy, which fetches it | The full request and response |
| HTTPS via CONNECT | The client sends CONNECT example.com:443, then negotiates TLS through the tunnel | Only the destination host and port, and encrypted bytes |
Authentication#
Credentials travel in the Proxy-Authorization header, base64-encoded; a proxy that wants them answers 407 Proxy Authentication Required. With IP whitelisting no header is needed, but the username can still carry targeting parameters.
Configuration#
http://USER-cc-us:PASS@res.hodlproxy.com:9000HTTP proxy or SOCKS5 proxy?#
Use an HTTP proxy for web traffic from libraries, browsers and scraping frameworks, which all support it natively. Use a SOCKS5 proxy when the client is not an HTTP tool or only offers a SOCKS setting. On HodlProxy the same credentials work on both: port 9000 (HTTP) or 9001 (SOCKS5) on the gateways, 8000 or 8001 on dedicated addresses.
How it works at HodlProxy#
HodlProxy gateways accept HTTP(S) on port 9000; dedicated addresses on port 8000. The same proxy URL works for http:// and https:// destinations.
Questions people ask#
Do I need a separate "HTTPS proxy"?
No. An HTTP proxy handles HTTPS destinations through CONNECT. "HTTPS proxy" sometimes means a proxy you reach over TLS yourself; most providers, HodlProxy included, do not offer TLS to the proxy port because the browser-to-site TLS already protects the content.
Can an HTTP proxy see my HTTPS traffic?
No. For HTTPS the client opens a CONNECT tunnel and negotiates TLS with the website through it; the proxy only sees the destination host name and encrypted bytes, unless it terminates TLS, which HodlProxy never does.
What is the difference between an HTTP proxy and a web proxy?
A web proxy usually means a website you browse through; an HTTP proxy is a server your own client is configured to use. The second is what proxy providers sell.