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
improve remote_addr behavior #2653
Conversation
…ad of LOCALHOST; when the client disconects unexpectedly, default to the unspecified source IP instead of localhost
Had a think about it and I think both of these changes are an improvement. However, they both have the potential to break people's setups, so I think we need to park these until 6.0. Your other option is to put one or both changes behind a temporary config option that we will remove in 6.0. I don't have a lot of insight right now on whether or not the next release will be a minor or major, so no promises on how long this could stay parked. Had one small concern about ipv6, see comment. |
…spec/localhost addresses
Removed waiting for review. This is only blocked on next major release. |
I'm thinking next release might be a major. |
Merged! |
Why not squash merging @nateberkopec ? |
Did it on the CLI and forgot 😆 |
Closes #2652
Description
See #2652 for details; this makes two changes:
set_remote_address header: "header_name"
functionality, if the header is not passed,REMOTE_ADDR
is now set to the physical peeraddr instead of always being set to 127.0.0.1REMOTE_ADDR
is now set to the unspecified source address ('0.0.0.0') instead of to '127.0.0.1'Your checklist for this pull request
[ci skip]
to the title of the PR.#issue
" to the PR description or my commit messages.