-
-
Notifications
You must be signed in to change notification settings - Fork 857
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
Can't handle URLs with @ character in userinfo section #328
Comments
Hi @sethmlarson I've pushed a PR about this topic. Could your review it? |
So, something I think we may want to re-review prior to 1.0 is which internal URL parsing implementation is really our best option. This issue (and perhaps also #858, although maybe that's exclusively an issue on our side?) currently means that we're a little less robust on URL parsing than the wonderfully battle hardened Making a change here wouldn't have any affect on our public API. That's tied down and looks that way we want. But this could potentially change which dependancies we choose to ship with. Some options here are...
Of those three options, the last seems like it'd be the most robust approach, since No doubt @sigmavirus24 and @sethmlarson both have far more insight into this, tho I don't want to push for anyone's time here. |
This is a common use-case for proxies and websites using email addresses as usernames for authentication.
This might require a change in
rfc3986
or the way we parse URLs. :)The text was updated successfully, but these errors were encountered: