What Is an HTTP Proxy?
An HTTP proxy is an intermediary that speaks HTTP to your client. It can forward normal HTTP requests and, when it supports CONNECT, open a tunnel to an HTTPS website.

How an HTTP Proxy Works
Your app needs the proxy’s host and port. For an HTTP destination, the proxy can read the request it forwards. For an HTTPS destination, an HTTP proxy can use CONNECT to create a tunnel. In ordinary tunnelling, TLS is established between your client and the website inside that tunnel. The proxy can still see connection details such as the destination.
Compare the Two Requests
These examples show what the client sends to an HTTP proxy on a network you control.
GET http://site.example/guide HTTP/1.1
Host: site.example
The proxy can read the full plain HTTP request, including the path and any headers. The destination sees the forwarded request from the proxy.
CONNECT site.example:443 HTTP/1.1
Host: site.example:443
After a successful CONNECT response, the client negotiates TLS with the destination inside the tunnel. The proxy sees the destination host and port, timing, and traffic volume. The destination decrypts the request and sees the path and headers. This example assumes normal TLS tunnelling without interception.
Follow an HTTP and HTTPS Request
- BrowserAsks the proxy for the full HTTP URL
- HTTP proxyReads and forwards the request
- OriginReturns the HTTP response
Plain HTTP does not encrypt the request or response. The proxy can see and change its contents.
- BrowserAsks the proxy to open a tunnel to the host and port
- HTTP proxyOpens a byte tunnel and sees its destination
- HTTPS originNegotiates TLS directly with the browser through the tunnel
In a normal CONNECT tunnel, the proxy sees the requested host and port but cannot read the encrypted HTTP content. An HTTPS proxy can separately encrypt the browser-to-proxy leg.
What HTTPS Proxy Can Mean
HTTPS destination support means the proxy can tunnel to an HTTPS website. TLS to the proxy means the first leg, from your app to the proxy, is also encrypted. Some proxy feeds use the same “HTTPS” label for different meanings. The label alone cannot establish which connection is encrypted.
HTTP vs SOCKS5
HTTP is the natural choice when the app exposes an HTTP proxy field or the service is designed around web requests. SOCKS5 can relay other TCP application protocols, subject to client and server support. Both require a proxy you trust.
Find HTTP Entries
Open the HTTP-filtered directory or view entries the feed labels HTTPS. Match the protocol to your app’s settings and read the directory’s protocol labels before relying on a label.
