Skip to content
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

Closed
mikael-lindstrom opened this issue May 5, 2015 · 1 comment · Fixed by #1650
Closed

[Core] Hardcoded no_proxy setting causes problems for EC2 metadata #1594

mikael-lindstrom opened this issue May 5, 2015 · 1 comment · Fixed by #1650
Milestone

Comments

@mikael-lindstrom
Copy link

Following this pull request: #1518
no_proxy is now hardcoded to 127.0.0.1,localhost in dogstatsd.py and emitter.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. If http_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 append 127.0.0.1,localhost if they are missing.

@LeoCavaille
Copy link
Member

👍 thanks for reporting.

@LeoCavaille LeoCavaille added this to the 5.4.0 milestone May 7, 2015
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
@remh remh closed this as completed in #1650 Jun 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants