-
Notifications
You must be signed in to change notification settings - Fork 813
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
[Core] Hardcoded no_proxy setting causes problems for EC2 metadata #1594
Comments
👍 thanks for reporting. |
remh
added a commit
that referenced
this issue
May 29, 2015
Fix #1594 Also: * simplify the proxy parsing * Move the code in a new utils module
remh
added a commit
that referenced
this issue
Jun 1, 2015
Fix #1594 Also: * simplify the proxy parsing * Move the code in a new utils module
remh
added a commit
that referenced
this issue
Jun 1, 2015
Fix #1594 Also: * simplify the proxy parsing * Move the code in a new utils module
remh
added a commit
that referenced
this issue
Jun 1, 2015
Fix #1594 Also: * simplify the proxy parsing * Move the code in a new utils module
remh
added a commit
that referenced
this issue
Jun 2, 2015
Fix #1594 Also: * simplify the proxy parsing * Move the code in a new utils module
remh
added a commit
that referenced
this issue
Jun 2, 2015
Fix #1594 Also: * simplify the proxy parsing * Move the code in a new utils module
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following this pull request: #1518
no_proxy
is now hardcoded to127.0.0.1,localhost
indogstatsd.py
andemitter.py
Since this is set in the environment it affects fetching of EC2 metadata on AWS as that is fetched from
169.254.169.254
. Ifhttp_proxy
is set, these requests will be sent through the proxy and return incorrect metadata.This should be changed to respect addresses set in
no_proxy
and only append127.0.0.1,localhost
if they are missing.The text was updated successfully, but these errors were encountered: