On Tue, 29 Sep 2009, Matthieu Moy wrote:
Unfortunately, it seems the complete URL is passed to curl, and curl is the one doing it wrong. Indeed: $ curl -v https://user@xxxxxxxxx@server.com/path/ * getaddrinfo(3) failed for email.com@xxxxxxxxxx:443
This is not exactly curl "doing it wrong". This is a user passing in something that isn't a URL to the command that asks for a URL to work on. The user part cannot legally have a '@' letter in a URL, you must encode it.
In short, you have to use %40 to escape the @, and curl does it this way because the RFC doesn't allow @ in usernames.
Exactly. So curl is not "wrong", it just can't work around this user-error. -- / daniel.haxx.se -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html