Protocols
Explore supported Mobile Proxy protocols and learn how to configure HTTP, HTTPS, HTTP/3, and SOCKS5 connections.
HTTP
Our documentation includes code examples showcasing how to connect to the proxies using HTTP protocol. The protocol is supported by common libraries and third-party software.
HTTPS
You can also use the fully encrypted connection using HTTPS protocol for an extra layer of security. For that, you have to add https:// to your proxy entry point. For example: https://pr.oxylabs.io:7777 (this also applies to country specific entry nodes).
Please note that some libraries (or their older versions) and some 3rd party tools may not support HTTPS protocol, so double-check before making changes to your code.
HTTP/3
HTTP3 is supported via proxies that can handle UDP traffic, as it is based on QUIC, a UDP-based transport protocol.
Standard HTTP/HTTPS proxy endpoints are not compatible with HTTP3, so to proxy requests, you need to use a SOCKS5 proxy with UDP traffic support, available through the following dedicated endpoint:
socks.pr.oxylabs.io:7777Most common tools do not natively support HTTP3 over SOCKS5 with UDP, so custom implementations may be required, such as our custom HTTP/3 Go, C#, and Java solution repositories on GitHub.
SOCKS5
SOCKS5proxy authentication is not supported by Google Chrome. Use Mozilla Firefox or HTTP clients instead.Certain target websites can identify proxy traffic using
SOCKS5. If you encounter connection errors, switch toHTTPorHTTPS.
Oxylabs Mobile Proxies support SOCKS5 connections over TCP and UDP.
For a SOCKS5 connection, use socks5h:// with your connection string:
Location targeting
SOCKS5 does not support country-specific entry point domains. To target a specific location, include the additional parameters within your username (e.g., France):
Ports of proxies
The default configuration of proxy ports includes 80 and 443, which are standard ports designed to accommodate the HTTP and HTTPS protocols, as outlined in the table below. To access other ports, it is necessary to undergo compliance verification, please contact our support.
HTTP
80
HTTPS
443
Last updated
Was this helpful?

