An HTTP proxy is an application-layer intermediary that receives HTTP requests and forwards them to destination servers. Because it understands HTTP methods and headers, it can apply rules based on the requested host, path, or other message details.

For an unencrypted HTTP destination, a client can send the proxy a request containing the full destination URL. For an HTTPS destination, the client usually sends the CONNECT method to ask the proxy for a TCP tunnel to the destination host and port. The client then performs TLS through that tunnel, so an ordinary forward proxy relays the encrypted bytes without seeing the protected HTTP content. That destination tunnel does not encrypt credentials sent over an HTTP connection between the client and proxy gateway.

HTTP proxies fit tools and libraries with built-in HTTP proxy settings. SOCKS5 proxies work at a lower layer and can relay more than HTTP, but they require SOCKS support in the client. The protocol chosen between client and proxy is separate from whether the destination connection uses HTTPS.

PacketStream provides its HTTPS proxy endpoint at proxy.packetstream.io:31111; HTTP is available on port 31112. Both use username and auth-key authentication. Use the HTTPS endpoint to encrypt those credentials between the client and proxy gateway. Read HTTPS versus SOCKS5 proxies for the differences and endpoints and authentication for connection details.

Related terms: SOCKS5 proxy and proxy server.

Browse all glossary terms

Use residential proxies with your own workflow.