-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
XFF_DEPTH_ENV #4357
XFF_DEPTH_ENV #4357
Conversation
@@ -18,6 +18,7 @@ export default function ({ | |||
host: host_env = 'HOST', | |||
port: port_env = 'PORT', | |||
origin: origin_env = 'ORIGIN', | |||
xffDepth: xff_depth_env = 'XFF_DEPTH', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No objections to this because I know it's consistent with the others, but it really seems unnecessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i guess the question becomes 'why is it necessary for the others but not this?' and if it isn't necessary for the others, then why do we need to make the env vars configurable at all?
|
* [breaking] rename xForwardedForIndex to xForwardedForNumProxies * add back link to blog post * changeset * update based on code review * update changeset * XFF_DEPTH_ENV (#4357) * use XFF_DEPTH_ENV * get rid of get_xff_depth * typo * Update packages/adapter-node/README.md Co-authored-by: Maurício Kishi <mrkishi@users.noreply.github.com> * Update packages/adapter-node/README.md * Update README.md * overhaul readme Co-authored-by: Rich Harris <richard.a.harris@gmail.com> Co-authored-by: Maurício Kishi <mrkishi@users.noreply.github.com> Co-authored-by: Rich Harris <hello@rich-harris.dev>
suggested changes to #4332 (cc @benmccann)