HTTP, HTTPS, or SOCKS5) can be specified in the tool or program you’re using to connect with the proxies.
In the following cURL examples, the protocol is specified at the beginning of the proxy line, just replace the username and password with your proxy user credentials, and run them in your Terminal or Command Prompt.
HTTP
Here is acURL example for the HTTP protocol:
cURL
HTTPS
Using this protocol will encrypt your connection. Here is acURL example for the HTTPS protocol:
cURL
SOCKS5
Here is acURL command for the SOCKS5 protocol:
cURL
The letter
h in socks5h:// means that the hostname will be resolved on the proxy side, and not locally.HTTP/3
HTTP/3 protocol is running over QUIC (UDP) traffic that is being tunneled through SOCKS5. HTTP and HTTPS endpoints are not supported with HTTP/3.
Use the socks5-gate.decodo.com endpoint on port 10000 for HTTP/3, and just replace the username and password with your proxy user credentials copied from your dashboard.
Here is a script in Go, which performs an HTTP/3 request through the proxy:
Ports
Easily understand which ports you can access when using our proxies, including details on the default accessible ports, restrictions, and how to request a port to be unblocked.Accessible Ports
With the residential and mobile proxies, the following ports are accessible by default:80443
Restricted Ports
Port Unblocking Process
To request a port unblock, contact us at compliance@decodo.com and provide the following information:- The port that needs to be unblocked.
- Describe the use case with that port – be as specific as possible.
- Provide the target that you’ll access using the mentioned port.
Please note that certain ports, such as those categorized as restricted, cannot be unblocked. Although the specific ports aren’t mentioned in this article, your request to unblock them may be denied.