You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ed78cb8
Browse filesBrowse the repository at this point in the historyBrowse files
| `log_sensitive_data` | Log full request URLs, upstream errors, and rejected Basic Auth username/password; disabled by default |
214
+
| `privacy_mode` | Strip client-IP/forwarding headers and suppress `Via` for proxy-visible HTTP metadata |
211
215
| `max_connections` | Maximum simultaneous client TCP connections |
212
216
| `max_connections_per_ip` | Maximum simultaneous client connections per source IP |
213
217
| `max_tunnels` | Maximum simultaneous CONNECT tunnels |
@@ -238,6 +242,12 @@ Timeout values use Go duration syntax, for example `500ms`, `10s`, or `2m`. Unkn
238
242
239
243
By default, request URL userinfo and query parameters are removed from logs, upstream errors are reduced to their HTTP category, and rejected Basic Auth credentials are not logged. For temporary diagnostics, set`log_sensitive_data: true` or `PROXY_LOG_SENSITIVE_DATA=true`. This can expose passwords and tokens in plaintext logs; disable it immediately after debugging.
240
244
245
+
### Privacy mode
246
+
247
+
Set `privacy_mode: true` or `PROXY_PRIVACY_MODE=true` to remove known client-address forwarding metadata from ordinary HTTP requests and trailers, including RFC `Forwarded`, `Via`, `X-Forwarded-*`, `X-Real-IP`, `True-Client-IP`, CDN connecting-IP headers, and common vendor equivalents. The proxy also omits its own `Via` header and does not forward a `Via` chain to an upstream proxy.
248
+
249
+
This is best-effort header privacy, not full anonymity. HTTPS/WSS traffic inside CONNECT is encrypted end-to-end, so the proxy cannot remove cookies, authorization headers, browser fingerprints, or application identifiers without acting as a TLS interception proxy. Browser traffic outside HTTP/HTTPS/WS/WSS, including WebRTC or other UDP paths, can bypass a web proxy. Sites can also classify the server's public IP as hosting, VPN, or proxy infrastructure.
250
+
241
251
### Resource limits and destination policy
242
252
243
253
Connection and CONNECT limits are enforced globally and per source IP. Excess TCP connections are closed immediately; excess tunnels and rate-limited authentication attempts receive `429 Too Many Requests`. A tunnel is closed when no bytes flow in either direction for `tunnel_idle_timeout`. Unless explicitly overridden, the HTTP/2 SETTINGS stream limit is derived from the lower tunnel limit so clients do not open streams that the proxy would immediately reject.
0 commit comments