Closed ghost closed 9 years ago
Totally agree, but as you mention, this is due to the parsing and escaping done by Go's stdlib. Once/if the bug is fixed in Go, this will be fixed too. Not a purell bug per se.
I believe that purell should use its own implementation of url.Parse/url.String and not rely on the buggy stdlib.
Pull requests welcome.
purell should not normalize reserved characters, as per RFC3986:
The above code outputs
my_%28url%29
, whereas it should bemy_(url)
. This is due to a bug in Go stdlib (issue 5684).