> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/dai-li/lian-jie-lei-xing.md).

# 连接类型

我们提供两种代理连接类型：轮换和粘性。

### 轮换

每次新请求时，IP 地址会自动更换。

您应使用：

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>用于 HTTP/HTTPS</td><td><strong>823</strong> 端口</td><td></td><td></td></tr><tr><td>用于 SOCKS5</td><td><strong>824</strong> 端口</td><td></td><td></td></tr></tbody></table>

<figure><img src="https://838239289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2PNbkVMJTPjkWGv2Kbvj%2Fuploads%2FxaFpg37IOci7ozuGfNj5%2FGoogle%20Chrome%202024-11-06%20%D0%B2%2009.46.33.png?alt=media&amp;token=34a3a197-8c87-475c-8452-14e3653cdf61" alt=""><figcaption></figcaption></figure>

***

### **粘性**

粘性代理基于端口。IP 地址在一段时间内绑定到特定端口。&#x20;

粘性代理的轮换间隔可以从 1 到 120 分钟不等，平均持续时间为 30 分钟。

对于粘性连接，您可以使用从 **10000** 到 **20000**.

HTTP 粘性代理示例：

```
curl -x "http://login:password@gw.dataimpulse.com:10000" https://api.ipify.org/
```

SOCKS5 粘性代理示例：

```
curl -x "socks5://login:password@gw.dataimpulse.com:10000" https://api.ipify.org/
```

{% hint style="info" %}
如果未为粘性连接指定轮换间隔或将其设置为 "0"，默认间隔为 30 分钟。
{% endhint %}

***

<figure><img src="https://838239289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2PNbkVMJTPjkWGv2Kbvj%2Fuploads%2FmF8SUohvv3OVtohiCfiv%2FGoogle%20Chrome%202024-11-06%20%D0%B2%2009.36.29.png?alt=media&amp;token=c0d5f2c6-8f79-4634-9e85-79fc17f98e19" alt=""><figcaption></figcaption></figure>

关于选择最佳代理类型的博客文章：

[轮换代理还是粘性代理：如何选择合适的选项](https://dataimpulse.com/blog/rotating-or-sticky-proxies-how-to-make-the-right-choice/)

<br>


---

# 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://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/dai-li/lian-jie-lei-xing.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.
