Docs: rproxy runs behind any TLS-terminating reverse proxy (closes #388)
check / check (push) Failing after 2m26s
check / check (push) Failing after 2m26s
README, SPEC and docs no longer present traefik as the required front proxy, and call it the TLS-terminating proxy. The README section of that name lists what the proxy must do: forward plain HTTP to port 8080, keep Host, set X-Forwarded-For and X-Forwarded-Proto, close an unused connection in under 120 seconds, and connect from an address in SWW_RPROXY_TRUSTED_PROXIES. traefik, Caddy and nginx appear as examples, with the Caddy and nginx settings their defaults lack. Model: opus-5-5
This commit was merged in pull request #391.
This commit is contained in:
1 parent
53d9bf6af6
commit
a05a82b1af
4 files changed
+100
-53
No files matched your search
+2
-1
@@ -68,7 +68,8 @@ Every one of these lines has:
|
||||
### Request detail
|
||||
|
||||
- `request_id`: the id `rproxy` made for the request when it arrived.
|
||||
- `peer_ip`: the address of `rproxy`'s TCP peer, normally traefik.
|
||||
- `peer_ip`: the address of `rproxy`'s TCP peer, normally the TLS-terminating
|
||||
proxy.
|
||||
- `forwarded_for`: the `X-Forwarded-For` header the visitor's request came with.
|
||||
- `client_group`: the client as rate limiting counts it, an IPv4 address as a
|
||||
/32 or an IPv6 group.
|
||||
|
||||
Reference in new issue
Block a user