-
Notifications
You must be signed in to change notification settings - Fork 331
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
Does not return ParseError for invalid Url #552
Comments
I haven’t looked in details, but it may be that the set of strings that successfully parse as a URL in the URL Standard (which this crate implements, though it’s behind on some spec changes) is not the same as the set of strings that match the |
Here are few other ones that parse successfully, but are likely invalid (via seanmonstar/reqwest#668 (comment)): "http://‘nvme@nip2"
"http://-1@"
"https://a@b"
"https://€@qq" |
I discovered that Opened this issue for it: #554 |
Outputs:
The text was updated successfully, but these errors were encountered: