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

netrc parsing is overly strict #717

Closed
ianwremmel opened this issue Oct 1, 2018 · 3 comments
Closed

netrc parsing is overly strict #717

ianwremmel opened this issue Oct 1, 2018 · 3 comments
Labels
blocked by upstream The issue is in a dependency. We are waiting for the upstream library to lay the groundwork.

Comments

@ianwremmel
Copy link

it appears that auth via netrc is broken if ~/.netrc includes entries that are not exactly login/password tuples. For example, I have the following entries for circle ci and heroku:

machine api.heroku.com
  login <redacted>
  password <redacted>
  method interactive
machine circleci.com
  login <redacted>

both of these entries prevent my entry for github.com from working with httpie (but curl works just fine).

@randall-fulton
Copy link

This is actually an issue with the requests package, which is the dependency implementing the ~/.netrc functionality. You should probably create this issue over there, and then it can eventually be updated here, once the requests version is upgraded.

@ianwremmel
Copy link
Author

opened psf/requests#4813

@ianwremmel
Copy link
Author

Now opened as https://bugs.python.org/issue34908?

@jkbrzt jkbrzt added the blocked by upstream The issue is in a dependency. We are waiting for the upstream library to lay the groundwork. label Nov 2, 2018
@jkbrzt jkbrzt closed this as completed Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked by upstream The issue is in a dependency. We are waiting for the upstream library to lay the groundwork.
Projects
None yet
Development

No branches or pull requests

3 participants