Reaching an HTTPS website through an HTTP proxy
With a client such as curl, an HTTPS request through an HTTP proxy usually uses a CONNECT tunnel. The TLS connection to the destination website then passes through that tunnel. This does not mean the initial connection to the proxy itself uses HTTPS: distinguish the gateway scheme from the target website scheme.
What SOCKS5 changes
SOCKS5 works at a different level to establish the connection requested by the client. It does not automatically translate the settings of software designed only for HTTP proxies. Check the accepted formats, supplied port and authentication method before changing your configuration. Do not assume HTTP access also supports SOCKS5.
socks5 and socks5h in curl
In curl, socks5:// resolves the destination hostname on the client, while socks5h:// passes that hostname to the proxy for resolution. This difference can change the DNS path and should be a deliberate choice. It does not configure DNS for your entire computer and, by itself, does not guarantee encryption or anonymity.
Record the exact configuration
Keep the host, port, protocol and credentials as separate fields. If the access you receive does not work, check these four items first. An incorrect protocol can produce a connection error before the website responds. In ProxyCrest, access details are available after delivery; resource center examples remain generic until access has been tested.
Frequently asked questions
Does HTTP mean I cannot open an HTTPS website?
No. An HTTP proxy that supports CONNECT can carry a tunnel to an HTTPS website. The exact capability depends on the gateway.
Does SOCKS5 encrypt all my traffic?
No. Encryption depends in part on the application protocol, such as TLS for HTTPS. The SOCKS5 name alone does not guarantee the confidentiality of all data.