-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reverse proxy support #189
Labels
feature
New feature or functionality that didn't exist.
Comments
jevolk
added a commit
to jevolk/charybdis
that referenced
this issue
Feb 24, 2023
jevolk
added a commit
to jevolk/charybdis
that referenced
this issue
Feb 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a request contains either the
X-Forwarded-For
orForwarded
headers and the originating host is trusted, the client IP should be derived from there instead.There needs to be a configuration option for trusting IPs, subnets and a wildcard for when you can't know the proxy IP/range beforehand (i.e. AWS CloudFront).
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For
https://symfony.com/doc/current/deployment/proxies.html
https://expressjs.com/en/guide/behind-proxies.html
The text was updated successfully, but these errors were encountered: