> 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/es/proxies/datacenter-proxies/protocols.md).

# Protocolos

Explora los protocolos compatibles de Datacenter Proxy y aprende a configurar conexiones HTTP, HTTPS y SOCKS5.

### HTTP

Nuestra documentación incluye ejemplos de código que muestran cómo conectarse a los proxies usando `HTTP` el protocolo. El protocolo es compatible con bibliotecas comunes y software de terceros.

### HTTPS

También puedes usar la conexión totalmente cifrada al proxy usando `HTTPS` el protocolo. Para ello, debes añadir `https://` a tu punto de entrada de proxy. Por ejemplo: `https://dc.oxylabs.io:8000`

<pre class="language-sh"><code class="lang-sh"><strong>curl -x https://dc.oxylabs.io:8000 -U user-USERNAME:PASSWORD https://ip.oxylabs.io/location 
</strong></code></pre>

### SOCKS5

El protocolo SOCKS5 admite ambas `TCP` y `UDP` conexiones.

Para usar `SOCKS5` el protocolo, debes añadir `socks5h://` a tu punto de entrada de proxy. Por ejemplo: `socks5h://dc.oxylabs.io:8000`

```bash
curl -x socks5h://dc.oxylabs.io:8000 -U user-USERNAME:PASSWORD https://ip.oxylabs.io/location
```


---

# 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/es/proxies/datacenter-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.