Upgrade to kaya 0.0.3 with trusted-proxy forwarded header support
CI / Build and push docker image (push) Successful in 1m25s
CI / Build and push docker image (push) Successful in 1m25s
- bump kaya-core/kaya-rsgi to >= 0.0.3 and add kaya-forwarded: forwarded header handling is no longer built into core, it is opt-in via ForwardedHeadersMixin and gated on trusted proxy CIDRs - add TRUSTED_PROXY_CIDRS setting (comma-separated CIDRs, validated at startup; empty means no proxy is trusted) and wire the mixin in app.py - cover trusted/untrusted peers, all-trusted chains and the RFC 7239 Forwarded header with port in the test suite - document the new variable in README, .env.example and docker-compose.yml
This commit is contained in:
@@ -1,3 +1,8 @@
|
||||
# Name used in the HTML page title/heading and the curl examples
|
||||
# (e.g. "ifconfig.me" when deployed under that domain).
|
||||
SITE_NAME=pyfconfig
|
||||
|
||||
# Comma-separated CIDRs/IPs of trusted reverse proxies. Forwarded /
|
||||
# X-Forwarded-* headers are honored only when the direct peer belongs to
|
||||
# one of these; leave empty when the app is directly exposed.
|
||||
# TRUSTED_PROXY_CIDRS=127.0.0.1,10.0.0.0/8
|
||||
|
||||
Reference in New Issue
Block a user