yeyinlaoying/goproxy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
arraykeys
2022-08-02 14:59:02 +08:00
parent 01df49e080
commit 9294245e6a
8 changed files with 65 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+14 -10
View File
@@ -1904,8 +1904,8 @@ The proxy's http(s)/socks5/sps proxy function supports user-to-agent access via
### What can I do through the API?
- User dimension, which controls the single connection rate and controls the maximum number of connections.
- IP dimension, which controls the single connection rate and controls the maximum number of connections.
- User dimension, which controls the single connection rate and controls the maximum number of connections, max connections count per seconds (QPS).
- IP dimension, which controls the single connection rate and controls the maximum number of connections, max connections count per seconds (QPS).
- Dynamic upstream, can dynamically obtain its upstream from the API according to the user or client IP, and support http(s)/socks5/ss upstream.
- Authenticate every connection, regardless of whether client authentication is required.
- Cache authentication results, time can be set to reduce API pressure.
@@ -1962,19 +1962,23 @@ if($ok){
header("ipconns:2000");
header("userrate:3000");
header("iprate:8000");
header("outgoing:http://127.0.0.1:3500?parent-type=tcp");
header("userqps:5");
header("ipqps:2");
header("upstream:http://127.0.0.1:3500?parent-type=tcp");
header("outgoing:1.1.1.1");
header("HTTP/1.1 204 No Content");
}
```
#### Explanation
userconns: The maximum number of connections for the user, not limited to 0 or not set this header.
ipcons: The maximum number of connections for the user IP, not limited to 0 or not set this header.
userrate: User's single TCP connection rate limit, in bytes/second, is not limited to 0 or does not set this header.
iprate: The single TCP connection rate limit of the user IP, in bytes/second, not limited to 0 or not set this header.
upstream: The upstream used, not empty, or not set this header.
outgoing: The outgoing ip，this option only working which upstream is empty. And the IP must belong to the machine running proxy。
#### HTTP HEADER Explanation
`userconns`: The maximum number of connections for the user, not limited to 0 or not set this header.
`ipcons`: The maximum number of connections for the user IP, not limited to 0 or not set this header.
`userrate`: User's single TCP connection rate limit, in bytes/second, is not limited to 0 or does not set this header.
`iprate`: The single TCP connection rate limit of the client IP, in bytes/second, not limited to 0 or not set this header.
`userqps`: The maximum number of connections per second (QPS) for the user, not limited to 0 or not set this header.
`ipqps`: The maximum number of connections per second (QPS) for the client IP, not limited to 0 or not set this header.
`upstream`: The upstream used, not empty, or not set this header.
`outgoing`: The outgoing ip，this option only working which upstream is empty. And the IP must belong to the machine running proxy。
#### Tips
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.