We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Curl does not use different credentials on this:
curl -n ftp://foouser@example.com curl -n ftp://baruser@example.com
Almost all clients (wget, lftp, ftp, ...) pick the matching entry out of ~/.netrc, but curl just takes the first ~/.netrc entry for "example.com".
Or, as a standalone example, using http:
cat > curl.netrc <<EOF machine example.com login foouser password foouser machine example.com login baruser password baruser EOF #> curl -qsS --netrc-file curl.netrc --trace-ascii - http://baruser@example.com | grep "user" == Info: Server auth using Basic with user 'foouser' #> curl -qsS --netrc-file curl.netrc --trace-ascii - http://foouser@example.com | grep "user" == Info: Server auth using Basic with user 'foouser'
curl 7.79.1
The text was updated successfully, but these errors were encountered:
url: given a user in the URL, find pwd for that user in netrc
ef4c6ed
Add test 380 to verify Reported-by: Manfred Schwarb Fixes #8241
3ffca6c
Add test 380 and 381 to verify, edited test 133 Reported-by: Manfred Schwarb Fixes #8241 Closes #8243
d1237ac
bagder
Successfully merging a pull request may close this issue.
Curl does not use different credentials on this:
Almost all clients (wget, lftp, ftp, ...) pick the matching entry out of ~/.netrc,
but curl just takes the first ~/.netrc entry for "example.com".
Or, as a standalone example, using http:
curl/libcurl version
curl 7.79.1
The text was updated successfully, but these errors were encountered: