每当针对不允许或未与正确产品一起使用的网站时，我们的系统将阻止该请求或将其从超级代理 IP （super proxy) 路由。
在这种情况下，您尝试访问的目标站点将看到来自超级代理的请求，并且可能会阻止请求或提供错误的IP地理位置。
为了更好地了解请求是否通过，只需在 curl 模式下检查请求：
- 转到 亮数据 API 和示例页面
- 选择 “shell” 作为示例，以及您将使用的正确网络类型 (api_exam.png)
- 复制 Curl 命令并在终端使用 -v 运行它
- 检查 x-Luminati-IP 的响应标头：
下面的代码片段显示了对被超级代理绕过的网站的 curl 请求，而不是由对等 IP 发送的:
curl --proxy zproxy.lum-superproxy.io:22225 --proxy-user lum-customer-c_9cf9551e-zone-resi:468fuw0cr5zu "https://www.google.com" -v -L
* Trying 95.179.153.203:22225...
* TCP_NODELAY set
* Connected to zproxy.lum-superproxy.io (95.179.153.203) port 22225 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to www.google.com:443
* Proxy auth using Basic with user 'lum-customer-c_9cf9551e-zone-resi'
> CONNECT www.google.com:443 HTTP/1.1
> Host: www.google.com:443
> Proxy-Authorization: Basic bHVtLWN1c3RvbWVyLWNfOWNmOTU1MWUtem9uZS1yZXNpOjQ2OGZ1dzBjcjV6dQ==
> User-Agent: curl/7.68.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 OK
< x-luminati-ip: superproxy bypass
< x-luminati-timeline: z6164-init:0,auth:83,dns_resolve:1
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CONNECT phase completed!
* CONNECT phase completed!
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=www.google.com
* start date: Dec 27 08:11:32 2021 GMT
* expire date: Mar 21 08:11:31 2022 GMT
* subjectAltName: host "www.google.com" matched cert's "www.google.com"
* issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x56124223ce10)
> GET / HTTP/2
> Host: www.google.com
> user-agent: curl/7.68.0
> accept: */*
Categories