-
Notifications
You must be signed in to change notification settings - Fork 6
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
Provide accurate handling of the Remote address information #16
Comments
jrconlin
added a commit
that referenced
this issue
Sep 6, 2018
jrconlin
added a commit
that referenced
this issue
Sep 6, 2018
jrconlin
added a commit
that referenced
this issue
Sep 6, 2018
jrconlin
added a commit
that referenced
this issue
Sep 7, 2018
jrconlin
added a commit
that referenced
this issue
Sep 19, 2018
feat: fixup testing around meta and geoip lookup * added discrete remote ip parser. * update README.md, fix `test_chan` to test in one pass. * add better comments * fix ip lookup to match specification lookups * set the `trusted_proxy_list` to use CIDRs Closes #16
jrconlin
added a commit
that referenced
this issue
Oct 2, 2018
feat: fixup testing around meta and geoip lookup * added discrete remote ip parser. * update README.md, fix `test_chan` to test in one pass. * add better comments * fix ip lookup to match specification lookups * set the `trusted_proxy_list` to use CIDRs Closes #16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it appears that actix takes a very simple view of how the remote address is resolved, which may lead to potential header spoofing. We may want to handle extracting the remote IP address from the request headers ourselves.
The text was updated successfully, but these errors were encountered: