Note that the Path field is stored in decoded form: /%47%6f%2f becomes /Go/. A consequence is that it is impossible to tell which slashes in the Path were slashes in the raw URL and which were %2f. This distinction is rarely important, but when it is, code must not use Path directly. The Parse function sets both Path and RawPath in the URL it returns, and URL's String method uses RawPath if it is a valid encoding of Path, by calling the EscapedPath method.

If you need this behaviour, try replacing that line with the following and seeing if that works:

	path := req.URL.EscapedPath() 

@uriklagnes You might find this interesting if you are using or can use a gorilla/mux Router. There is this setting available for it:
UseEncodedPath

UseEncodedPath tells the router to match the encoded original
path to the routes.
For eg. "/path/foo%2Fbar/to" will match the path "/path/{var}/to".

If not called, the router will match the unencoded path to the
routes. For eg. "/path/foo%2Fbar/to" will match the path 
"/path/foo/bar/to"

Judging from the description it seems to solve your problem. I'm soon gonna try it out.

@uriklagnes You might find this interesting if you are using or can use a gorilla/mux Router. There is this setting available for it:
UseEncodedPath

UseEncodedPath tells the router to match the encoded original
path to the routes.
For eg. "/path/foo%2Fbar/to" will match the path "/path/{var}/to".

If not called, the router will match the unencoded path to the
routes. For eg. "/path/foo%2Fbar/to" will match the path 
"/path/foo/bar/to"

Judging from the description it seems to solve your problem. I'm soon gonna try it out.

I can confirm that the gorilla/mux router solves this problem. It would be nice if httprouter supports this too.

I opened a PR to implement an option to enable this behavior