update
This commit is contained in:
arraykeys
@@ -13,18 +13,6 @@ The GoProxy is a high-performance http proxy, https proxy, socks5 proxy, ss prox
|
||||
|
||||
---
|
||||
|
||||
## 赞助者/Sponsors
|
||||
|
||||
<a target="_blank" href="https://www.capsolver.com/zh?utm_source=github&utm_medium=banner_github&utm_campaign=goproxy">
|
||||
<img src="/doc/images/zanzhu_capsolver.jpg" height="200">
|
||||
</a>
|
||||
|
||||
[Capsolver.com](https://www.capsolver.com/?utm_source=github&utm_medium=banner_github&utm_campaign=goproxy_github)是一家基于人工智能，提供自动验证码解决功能的服务商。支持的验证码类型包括reCAPTCHA、hCaptcha和FunCaptcha、
|
||||
hCaptcha Enterprise, FunCaptcha Enterprise, Cloudflare Challenge 5s / Turnstile Captcha, DataDome Captcha / Interstinial ,
|
||||
AWS captcha、Geetest、Akamai Web、BMP、Imperva/Incapsula、captcha图像识别等。
|
||||
|
||||
---
|
||||
|
||||
## 中文用户请看 *中文说明*，中文与英文内容的安装等资源链接是不一样的，谢谢合作！
|
||||
|
||||
### [点击我观看视频教程](https://space.bilibili.com/472844633)
|
||||
@@ -2098,10 +2086,15 @@ each client connection.
|
||||
1. By default, `--auth-url` is required to provide the user name and password. If you do not need the client to provide the username and password, and authenticate, you can add `--auth-nouser`. The visit will still access the authentication address `--auth-url` for authentication. Only the $user authentication username and the $pass authentication password received in the php interface are empty when client didn't send username and password.
|
||||
2. Connection limit priority: User authentication file limit - "File ip.limit limit -" API user limit - "API IP limit -" command line global connection limit.
|
||||
3. Rate Limit Priority: User Authentication File Rate Limit - "File ip.limit Rate Limit -" API User Rate Limit - "API IP Rate Limit - "Command Line Global Rate Limit.
|
||||
4. The upstream obtains the priority: the upstream of the user authentication file - the file ip.limit upstream-"API upstream-" command line specifies the upstream.
|
||||
5. `--auth-cache` authentication cache, cache the authentication result for a certain period of time, improve performance, reduce the pressure on the authentication interface, --auth-cache unit seconds, default 0, set 0 to close the cache.
|
||||
6. By default, `--auth-cache` only caches the results of successful authentication and does not cache the results of failed authentication. If you need to cache the failed authentication results for a certain period of time,
|
||||
It can be set through the parameter `-auth-fail-cache` to improve performance and reduce the pressure on the authentication interface. The unit of --auth-fail-cache is seconds. The default is 0. Setting 0 turns off the cache.
|
||||
4. The upstream obtains the priority: the upstream of the user authentication file - the file ip.limit upstream-"API
|
||||
upstream-" command line specifies the upstream.
|
||||
5. `--auth-cache` authentication cache, cache the authentication result for a certain period of time, improve
|
||||
performance, reduce the pressure on the authentication interface, --auth-cache unit seconds, default 0, set 0 to
|
||||
close the cache.
|
||||
6. By default, `--auth-cache` only caches the results of successful authentication and does not cache the results of
|
||||
failed authentication. If you need to cache the failed authentication results for a certain period of time,
|
||||
It can be set through the parameter `-auth-fail-cache` to improve performance and reduce the pressure on the
|
||||
authentication interface. The unit of --auth-fail-cache is seconds. The default is 0. Setting 0 turns off the cache.
|
||||
|
||||
#### upstream detailed description
|
||||
|
||||
|
||||
+2
-13
@@ -13,18 +13,6 @@ GoProxy是一款轻量级、功能强大、高性能的http代理、https代理
|
||||
|
||||
---
|
||||
|
||||
## 赞助者/Sponsors
|
||||
|
||||
<a target="_blank" href="https://www.capsolver.com/zh?utm_source=github&utm_medium=banner_github&utm_campaign=goproxy">
|
||||
<img src="/doc/images/zanzhu_capsolver.jpg" height="200">
|
||||
</a>
|
||||
|
||||
[Capsolver.com](https://www.capsolver.com/?utm_source=github&utm_medium=banner_github&utm_campaign=goproxy_github)是一家基于人工智能，提供自动验证码解决功能的服务商。支持的验证码类型包括reCAPTCHA、hCaptcha和FunCaptcha、
|
||||
hCaptcha Enterprise, FunCaptcha Enterprise, Cloudflare Challenge 5s / Turnstile Captcha, DataDome Captcha / Interstinial ,
|
||||
AWS captcha、Geetest、Akamai Web、BMP、Imperva/Incapsula、captcha图像识别等。
|
||||
|
||||
---
|
||||
|
||||
### [点击我观看视频教程](https://space.bilibili.com/472844633)
|
||||
|
||||
- [下载地址](https://github.com/snail007/goproxy/releases)
|
||||
@@ -2220,7 +2208,8 @@ if($ok){
|
||||
|
||||
#### 提示
|
||||
|
||||
1. 默认情况下，设置了`--auth-url`是强制要求客户端提供用户名和密码的；如果不需要强制要求客户端提供用户名密码，并认证，可以加上`--auth-nouser`，
|
||||
1. 默认情况下，设置了`--auth-url`
|
||||
是强制要求客户端提供用户名和密码的；如果不需要强制要求客户端提供用户名密码，并认证，可以加上`--auth-nouser`，
|
||||
每次访问仍然会访问认证地址`--auth-url`进行认证，当客户端没有发生认证信息当时候，php接口里面接收的$user认证用户名和$pass认证密码都为空。
|
||||
2. 连接数限制优先级：用户认证文件连接数限制-》文件ip.limit连接数限制-》API用户连接数限制-》API的IP连接数限制-》命令行全局连接数限制。
|
||||
3. 速率限制优先级：用户认证文件速率限制-》文件ip.limit速率限制-》API用户速率限制-》API的IP速率限制-》命令行全局速率限制。
|
||||
|
||||
@@ -1890,10 +1890,15 @@ each client connection.
|
||||
1. By default, `--auth-url` is required to provide the user name and password. If you do not need the client to provide the username and password, and authenticate, you can add `--auth-nouser`. The visit will still access the authentication address `--auth-url` for authentication. Only the $user authentication username and the $pass authentication password received in the php interface are empty when client didn't send username and password.
|
||||
2. Connection limit priority: User authentication file limit - "File ip.limit limit -" API user limit - "API IP limit -" command line global connection limit.
|
||||
3. Rate Limit Priority: User Authentication File Rate Limit - "File ip.limit Rate Limit -" API User Rate Limit - "API IP Rate Limit - "Command Line Global Rate Limit.
|
||||
4. The upstream obtains the priority: the upstream of the user authentication file - the file ip.limit upstream-"API upstream-" command line specifies the upstream.
|
||||
5. `--auth-cache` authentication cache, cache the authentication result for a certain period of time, improve performance, reduce the pressure on the authentication interface, --auth-cache unit seconds, default 0, set 0 to close the cache.
|
||||
6. By default, `--auth-cache` only caches the results of successful authentication and does not cache the results of failed authentication. If you need to cache the failed authentication results for a certain period of time,
|
||||
It can be set through the parameter `-auth-fail-cache` to improve performance and reduce the pressure on the authentication interface. The unit of --auth-fail-cache is seconds. The default is 0. Setting 0 turns off the cache.
|
||||
4. The upstream obtains the priority: the upstream of the user authentication file - the file ip.limit upstream-"API
|
||||
upstream-" command line specifies the upstream.
|
||||
5. `--auth-cache` authentication cache, cache the authentication result for a certain period of time, improve
|
||||
performance, reduce the pressure on the authentication interface, --auth-cache unit seconds, default 0, set 0 to
|
||||
close the cache.
|
||||
6. By default, `--auth-cache` only caches the results of successful authentication and does not cache the results of
|
||||
failed authentication. If you need to cache the failed authentication results for a certain period of time,
|
||||
It can be set through the parameter `-auth-fail-cache` to improve performance and reduce the pressure on the
|
||||
authentication interface. The unit of --auth-fail-cache is seconds. The default is 0. Setting 0 turns off the cache.
|
||||
|
||||
#### upstream detailed description
|
||||
|
||||
|
||||
@@ -1981,7 +1981,8 @@ if($ok){
|
||||
|
||||
#### 提示
|
||||
|
||||
1. 默认情况下，设置了`--auth-url`是强制要求客户端提供用户名和密码的；如果不需要强制要求客户端提供用户名密码，并认证，可以加上`--auth-nouser`，
|
||||
1. 默认情况下，设置了`--auth-url`
|
||||
是强制要求客户端提供用户名和密码的；如果不需要强制要求客户端提供用户名密码，并认证，可以加上`--auth-nouser`，
|
||||
每次访问仍然会访问认证地址`--auth-url`进行认证，当客户端没有发生认证信息当时候，php接口里面接收的$user认证用户名和$pass认证密码都为空。
|
||||
2. 连接数限制优先级：用户认证文件连接数限制-》文件ip.limit连接数限制-》API用户连接数限制-》API的IP连接数限制-》命令行全局连接数限制。
|
||||
3. 速率限制优先级：用户认证文件速率限制-》文件ip.limit速率限制-》API用户速率限制-》API的IP速率限制-》命令行全局速率限制。
|
||||
|
||||
Reference in New Issue
Block a user