Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
 snail007
|
e6d6a821db | ||
|
snail007
|
27af51353d | ||
|
snail007
|
cf0873e14e |
@@ -1834,7 +1834,21 @@ Translation:
|
||||
You can also use the parameter `--dns-interface` to specify the bandwidth used for dns resolution,
|
||||
for example: `--dns-interface eth0`, dns resolution will use the eth0 bandwidth, this parameter must be set to `--dns-address` to be effective.
|
||||
|
||||
### 6.21 Help
|
||||
### 6.21 Domain Name Sniffing
|
||||
|
||||
When a user client connects to the proxy using the SOCKS5 or HTTP proxy protocol, if the client connects with a domain name,
|
||||
the client can choose to resolve the domain name locally or through the proxy. If the client resolves the domain name locally
|
||||
and lets the proxy connect to the resolved IP, then the connection target obtained in the "API authentication" parameters will
|
||||
be the IP or empty.
|
||||
|
||||
To avoid this situation, proxy provides a domain name sniffing feature. When the client connects to the SPS proxy, whether
|
||||
through "HTTP proxy" or "SOCKS5 proxy", if the client accesses an http or https website, proxy will sniff the domain name
|
||||
from the transmitted data. The sniffed domain name will be placed in the `sniff_domain` parameter of the "traffic reporting"
|
||||
API, so the domain name can be obtained through the "traffic reporting" API.
|
||||
|
||||
To enable domain name sniffing, you can use the `--sniff-domain` parameter.
|
||||
|
||||
### 6.22 Help
|
||||
|
||||
`proxy help sps`
|
||||
|
||||
@@ -2192,7 +2206,7 @@ There are two reporting modes, which can be specified by the `--traffic-mode` pa
|
||||
|
||||
The following is a complete URL request example:
|
||||
|
||||
`http://127.0.0.1:33088/user/traffic?bytes=337&client_addr=127.0.0.1%3A51035&id=http&server_addr =127.0.0.1%3A33088&target_addr=myip.ipip.net%3A80&username=a`
|
||||
`http://127.0.0.1:33088/user/traffic?bytes=337&client_addr=127.0.0.1%3A51035&id=http&server_addr =127.0.0.1%3A33088&target_addr=myip.ipip.net%3A80&username=a&sniff_domain=myip.ipip.net`
|
||||
|
||||
**Request parameter description:**
|
||||
`id`: service id flag.
|
||||
@@ -2203,7 +2217,8 @@ The following is a complete URL request example:
|
||||
`bytes`: the number of traffic bytes used by the user.
|
||||
`out_local_addr`: outgoing tcp connection's local address,format: IP: port.
|
||||
`out_remote_addr`: outgoing tcp connection's remote address,format: IP: port.
|
||||
`upstream`: upstream used by outgoing tcp connection, if none upstream be used, it's empty.
|
||||
`upstream`: upstream used by outgoing tcp connection, if none upstream be used, it's empty.
|
||||
`sniff_domain`: This parameter is only available when the SPS function is enabled and the `--sniff-domain` option is used. The "sniff_domain" parameter is the sniffed domain name, in the format: domain or domain:port; this parameter only has a value when the client accesses an http/https URL, otherwise it is empty.
|
||||
|
||||
#### Tips
|
||||
|
||||
|
||||
+12
-3
@@ -1964,7 +1964,15 @@ iptables -t nat -A OUTPUT -p tcp -j PROXY
|
||||
|
||||
还可以用参数`--dns-interface`指定dns解析使用的网卡，比如：`--dns-interface eth0`，dns解析就会走eth0网卡，此参数必须设置`--dns-address`才有效。
|
||||
|
||||
### 6.21 查看帮助
|
||||
### 6.21 嗅探域名
|
||||
当用户客户端使用socks5代理或http代理协议连接代理的时候，客户端如果连接的是域名，这个时候客户端可以决定是本地解析域名还是通过代理解析域名，
|
||||
如果客户端使用本地解析域名，然后让代理连接解析后的IP，那么“API认证”的参数里面拿到的连接目标就是IP或者空；
|
||||
为了避免这种情况，proxy提供了一个域名嗅探功能，当客户端连接SPS代理的时候，无论是通过 “HTTP代理” 还是 “SOCKS5代理”，当客户端访问的是 http
|
||||
或 https 网址的时候，proxy 都会嗅探传输数据中的域名，嗅探到的域名会放在“流量上报”接口的`sniff_domain`参数里面，这样就可以在“流量上报”接口获取域名。
|
||||
|
||||
默认情况下，sps的域名嗅探功能是关闭的，如果需要开启，可以通过参数`--sniff-domain`开启。
|
||||
|
||||
### 6.22 查看帮助
|
||||
|
||||
`proxy help sps`
|
||||
|
||||
@@ -2299,7 +2307,7 @@ proxy会把连接使用的流量上报到这个地址,具体情况是,proxy发
|
||||
下面是一个完整的URL请求实例:
|
||||
|
||||
`http://127.0.0.1:8080/auth.php?act=traffic&bytes=7627&client_addr=127.0.0.1%3A63637
|
||||
&id=http&out_local_addr=127.0.0.1%3A63640&out_remote_addr=127.0.0.1%3A63639 &server_addr=127.0.0.1%3A33080&target_addr=www.baidu.com%3A443 &upstream=http%3A%2F%2F127.0.0.1%3A3100&username=a`
|
||||
&id=http&out_local_addr=127.0.0.1%3A63640&out_remote_addr=127.0.0.1%3A63639&server_addr=127.0.0.1%3A33080&target_addr=www.baidu.com%3A443&upstream=http%3A%2F%2F127.0.0.1%3A3100&username=a&sniff_domain=www.baidu.com`
|
||||
|
||||
**请求参数说明**:
|
||||
`id`: 服务id标志。
|
||||
@@ -2310,7 +2318,8 @@ proxy会把连接使用的流量上报到这个地址,具体情况是,proxy发
|
||||
`bytes`: 此次使用的流量字节数。
|
||||
`out_local_addr`: 代理对外建立的TCP连接的本地地址，格式: `IP:端口`。
|
||||
`out_remote_addr`: 代理对外建立的TCP连接的远程地址，格式: `IP:端口`。
|
||||
`upstream`: 使用的上级，格式是标准URL格式，如果没有使用上级，这里是空。
|
||||
`upstream`: 使用的上级，格式是标准URL格式，如果没有使用上级，这里是空。
|
||||
`sniff_domain`: 只有当 sps 功能，使用参数 `--sniff-domain` 开启了嗅探功能 ，才会有这个参数。参数“sniff_domain”是嗅探到的域名，格式：域名，或者： 域名:端口；只有在客户端访问的是 http/https 网址的时候这个参数才有值，其它情况为空。
|
||||
|
||||
#### 提示
|
||||
|
||||
|
||||
+18
-3
@@ -1636,7 +1636,21 @@ Translation:
|
||||
You can also use the parameter `--dns-interface` to specify the bandwidth used for dns resolution,
|
||||
for example: `--dns-interface eth0`, dns resolution will use the eth0 bandwidth, this parameter must be set to `--dns-address` to be effective.
|
||||
|
||||
### 6.21 Help
|
||||
### 6.21 Domain Name Sniffing
|
||||
|
||||
When a user client connects to the proxy using the SOCKS5 or HTTP proxy protocol, if the client connects with a domain name,
|
||||
the client can choose to resolve the domain name locally or through the proxy. If the client resolves the domain name locally
|
||||
and lets the proxy connect to the resolved IP, then the connection target obtained in the "API authentication" parameters will
|
||||
be the IP or empty.
|
||||
|
||||
To avoid this situation, proxy provides a domain name sniffing feature. When the client connects to the SPS proxy, whether
|
||||
through "HTTP proxy" or "SOCKS5 proxy", if the client accesses an http or https website, proxy will sniff the domain name
|
||||
from the transmitted data. The sniffed domain name will be placed in the `sniff_domain` parameter of the "traffic reporting"
|
||||
API, so the domain name can be obtained through the "traffic reporting" API.
|
||||
|
||||
To enable domain name sniffing, you can use the `--sniff-domain` parameter.
|
||||
|
||||
### 6.22 Help
|
||||
|
||||
`proxy help sps`
|
||||
|
||||
@@ -1994,7 +2008,7 @@ There are two reporting modes, which can be specified by the `--traffic-mode` pa
|
||||
|
||||
The following is a complete URL request example:
|
||||
|
||||
`http://127.0.0.1:33088/user/traffic?bytes=337&client_addr=127.0.0.1%3A51035&id=http&server_addr =127.0.0.1%3A33088&target_addr=myip.ipip.net%3A80&username=a`
|
||||
`http://127.0.0.1:33088/user/traffic?bytes=337&client_addr=127.0.0.1%3A51035&id=http&server_addr =127.0.0.1%3A33088&target_addr=myip.ipip.net%3A80&username=a&sniff_domain=myip.ipip.net`
|
||||
|
||||
**Request parameter description:**
|
||||
`id`: service id flag.
|
||||
@@ -2005,7 +2019,8 @@ The following is a complete URL request example:
|
||||
`bytes`: the number of traffic bytes used by the user.
|
||||
`out_local_addr`: outgoing tcp connection's local address,format: IP: port.
|
||||
`out_remote_addr`: outgoing tcp connection's remote address,format: IP: port.
|
||||
`upstream`: upstream used by outgoing tcp connection, if none upstream be used, it's empty.
|
||||
`upstream`: upstream used by outgoing tcp connection, if none upstream be used, it's empty.
|
||||
`sniff_domain`: This parameter is only available when the SPS function is enabled and the `--sniff-domain` option is used. The "sniff_domain" parameter is the sniffed domain name, in the format: domain or domain:port; this parameter only has a value when the client accesses an http/https URL, otherwise it is empty.
|
||||
|
||||
#### Tips
|
||||
|
||||
|
||||
@@ -1737,7 +1737,15 @@ iptables -t nat -A OUTPUT -p tcp -j PROXY
|
||||
|
||||
还可以用参数`--dns-interface`指定dns解析使用的网卡，比如：`--dns-interface eth0`，dns解析就会走eth0网卡，此参数必须设置`--dns-address`才有效。
|
||||
|
||||
### 6.21 查看帮助
|
||||
### 6.21 嗅探域名
|
||||
当用户客户端使用socks5代理或http代理协议连接代理的时候，客户端如果连接的是域名，这个时候客户端可以决定是本地解析域名还是通过代理解析域名，
|
||||
如果客户端使用本地解析域名，然后让代理连接解析后的IP，那么“API认证”的参数里面拿到的连接目标就是IP或者空；
|
||||
为了避免这种情况，proxy提供了一个域名嗅探功能，当客户端连接SPS代理的时候，无论是通过 “HTTP代理” 还是 “SOCKS5代理”，当客户端访问的是 http
|
||||
或 https 网址的时候，proxy 都会嗅探传输数据中的域名，嗅探到的域名会放在“流量上报”接口的`sniff_domain`参数里面，这样就可以在“流量上报”接口获取域名。
|
||||
|
||||
默认情况下，sps的域名嗅探功能是关闭的，如果需要开启，可以通过参数`--sniff-domain`开启。
|
||||
|
||||
### 6.22 查看帮助
|
||||
|
||||
`proxy help sps`
|
||||
|
||||
@@ -2072,7 +2080,7 @@ proxy会把连接使用的流量上报到这个地址,具体情况是,proxy发
|
||||
下面是一个完整的URL请求实例:
|
||||
|
||||
`http://127.0.0.1:8080/auth.php?act=traffic&bytes=7627&client_addr=127.0.0.1%3A63637
|
||||
&id=http&out_local_addr=127.0.0.1%3A63640&out_remote_addr=127.0.0.1%3A63639 &server_addr=127.0.0.1%3A33080&target_addr=www.baidu.com%3A443 &upstream=http%3A%2F%2F127.0.0.1%3A3100&username=a`
|
||||
&id=http&out_local_addr=127.0.0.1%3A63640&out_remote_addr=127.0.0.1%3A63639&server_addr=127.0.0.1%3A33080&target_addr=www.baidu.com%3A443&upstream=http%3A%2F%2F127.0.0.1%3A3100&username=a&sniff_domain=www.baidu.com`
|
||||
|
||||
**请求参数说明**:
|
||||
`id`: 服务id标志。
|
||||
@@ -2083,7 +2091,8 @@ proxy会把连接使用的流量上报到这个地址,具体情况是,proxy发
|
||||
`bytes`: 此次使用的流量字节数。
|
||||
`out_local_addr`: 代理对外建立的TCP连接的本地地址，格式: `IP:端口`。
|
||||
`out_remote_addr`: 代理对外建立的TCP连接的远程地址，格式: `IP:端口`。
|
||||
`upstream`: 使用的上级，格式是标准URL格式，如果没有使用上级，这里是空。
|
||||
`upstream`: 使用的上级，格式是标准URL格式，如果没有使用上级，这里是空。
|
||||
`sniff_domain`: 只有当 sps 功能，使用参数 `--sniff-domain` 开启了嗅探功能 ，才会有这个参数。参数“sniff_domain”是嗅探到的域名，格式：域名，或者： 域名:端口；只有在客户端访问的是 http/https 网址的时候这个参数才有值，其它情况为空。
|
||||
|
||||
#### 提示
|
||||
|
||||
|
||||
+6
-6
@@ -17,6 +17,12 @@
|
||||
<lastmod>2019-06-14T16:29:13+08:00</lastmod>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://snail007.goproxyauth.com/goproxy/tags/cdn/</loc>
|
||||
<lastmod>2019-07-05T08:20:48+08:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://snail007.goproxyauth.com/goproxy/categories/</loc>
|
||||
<lastmod>2019-07-05T08:20:48+08:00</lastmod>
|
||||
@@ -41,12 +47,6 @@
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://snail007.goproxyauth.com/goproxy/tags/cdn/</loc>
|
||||
<lastmod>2019-07-05T08:20:48+08:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://snail007.goproxyauth.com/goproxy/tags/cloudflare/</loc>
|
||||
<lastmod>2019-07-05T08:20:48+08:00</lastmod>
|
||||
|
||||
@@ -14,7 +14,7 @@
|
||||
<link href="//maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css" rel="stylesheet">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
|
||||
<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/8.4/styles/solarized_dark.min.css">
|
||||
<title>cdn - GOPROXY IN ACTION</title>
|
||||
<title>CDN - GOPROXY IN ACTION</title>
|
||||
|
||||
<link href="https://snail007.goproxyauth.com/goproxy/css/styles.css" rel="stylesheet">
|
||||
|
||||
@@ -77,7 +77,7 @@
|
||||
|
||||
|
||||
<header class="page-header">
|
||||
<h1>cdn</h1>
|
||||
<h1>CDN</h1>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>cdn on GOPROXY IN ACTION</title>
|
||||
<title>CDN on GOPROXY IN ACTION</title>
|
||||
<link>https://snail007.goproxyauth.com/goproxy/tags/cdn/</link>
|
||||
<description>Recent content in cdn on GOPROXY IN ACTION</description>
|
||||
<description>Recent content in CDN on GOPROXY IN ACTION</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>zh-CN</language>
|
||||
<lastBuildDate>Fri, 05 Jul 2019 08:20:48 +0800</lastBuildDate>
|
||||
|
||||
+1
-1
@@ -12,7 +12,7 @@
|
||||
|
||||
|
||||
<item>
|
||||
<title>cdn</title>
|
||||
<title>CDN</title>
|
||||
<link>https://snail007.goproxyauth.com/goproxy/tags/cdn/</link>
|
||||
<pubDate>Fri, 05 Jul 2019 08:20:48 +0800</pubDate>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user