-
Notifications
You must be signed in to change notification settings - Fork 18k
affected/package: url.Parse #51358
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
Comments
A url must begin with a scheme, ie, https://, a scheme must begin with a letter, https://datatracker.ietf.org/doc/html/rfc3986#section-3.1. 360.com does not begin with a scheme so it is not a valid URL. The other two examples are also not valid URLs
I believe this is working as intended. |
WAI Close #51358. |
Sorry, you are right, I did not read the notes carefully 😮💨 |
It can be a bit confusing because the *url.URL object has a String method which does its best to print the components of the URL it just parsed — it looked like the url was parsed correctly, but that was unfortunately an ambiguity in the url spec with colons that early in the string. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
The program to run normally.
What did you see instead?
The text was updated successfully, but these errors were encountered: