> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/proxies/mobile-proxies/protocols.md).

# 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**](/products/proxies/mobile-proxies/location-settings/country.md#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:7777
```

Most common tools do not natively support `HTTP3` over `SOCKS5` with `UDP`, so custom implementations may be required, such as our custom HTTP/3 [Go](https://github.com/oxylabs/gohttp3viaSOCKS5UDP), [C#](https://github.com/oxylabs/csharphttp3viaSOCKS5UDP), and [Java](https://github.com/oxylabs/javahttp3viaSOCKS5UDP) solution repositories on GitHub.

{% hint style="info" %}
**Note:** Make sure your firewall allows UDP traffic on the required ports, as many ports block UDP by default
{% endhint %}

## **SOCKS5**

{% hint style="warning" %}

* `SOCKS5` proxy 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 to `HTTP` or `HTTPS`.
  {% endhint %}

Oxylabs Mobile Proxies support `SOCKS5` connections over `TCP` and `UDP`.

{% hint style="info" %}
`UDP` setup may be more challenging, contact your dedicated Account Manager or [Customer Support](mailto:support@oxylabs.io) for assistance.
{% endhint %}

For a `SOCKS5` connection, use `socks5h://` with your connection string:

```bash
curl -x socks5h://pr.oxylabs.io:7777 -U "customer-USERNAME:PASSWORD" ip.oxylabs.io/location
```

#### Location targeting

`SOCKS5` does not support country-specific entry point domains. To target a specific location, include the [**additional parameters**](/products/proxies/mobile-proxies/making-requests.md) within your username (e.g., France):

```bash
curl -x socks5h://pr.oxylabs.io:7777 -U "customer-USERNAME-cc-FR:PASSWORD" ip.oxylabs.io/location
```

## 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**](mailto:support@oxylabs.io).

| Protocol | Port  |
| -------- | ----- |
| `HTTP`   | `80`  |
| `HTTPS`  | `443` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.oxylabs.io/products/proxies/mobile-proxies/protocols.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.