-
Notifications
You must be signed in to change notification settings - Fork 116
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
auth
: Add :netrc | {:netrc, path}
as possible values
#52
Comments
Let's still keep it as a distinct step, it's just auth/2 is going to use it under the hood. |
auth
: Add :netrc | {:netrc, path}
as possible values
Looking at this, I am not sure why keeping If you run both steps, it will send two authorization headers, which I believe is not consistent with RFC7230. It makes sense to me to keep |
Separate question -
But the documentation I can find here and here suggests it should be:
or
Should I stick with |
oops, it should have been |
Instead of having a distinct load_netrc step, make it an option to auth, e.g.:
auth: :netrc
which also would be the default?The text was updated successfully, but these errors were encountered: