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.proxy-cyber.com:9000How it works at Proxy Cyber#
Proxy Cyber 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, Proxy Cyber included, do not offer TLS to the proxy port because the browser-to-site TLS already protects the content.