-
Notifications
You must be signed in to change notification settings - Fork 58
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
Opaque URLs should be normalized too #8
Comments
I guess it should, to be honest I'm not sure I completely grasp the opaque field. I don't really have a need for it, but if someone cares enough to provide a PR (with tests), I'll be happy to merge. |
I feel this is an important issue and here's something related: u, _ := url.Parse("www.youtube.com")
fmt.Println(purell.NormalizeURL(u, purell.FlagsUsuallySafeGreedy)) will print |
This is indeed an important issue and is addressed in PR #5 (merged in fix-relative-paths branch for now, in master hopefully soon). This is unrelated to the Opaque field that is the subject of this issue, though (see e.g. http://play.golang.org/p/VP8o_CjrPA). |
Closing, I think the Opaque field is meant to be left untouched. The other issue discussed here by pkieltyka is fixed in master now. |
purell doesn't normalize "opaque"
URL
s (see documentation for url.URL).Output:
http://eXAMPLe.com/%3f
The text was updated successfully, but these errors were encountered: