Skip to content
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

Use req.URL.EscapedPath() instead of getPath(req) #306

Merged
merged 1 commit into from
Oct 20, 2017

Conversation

mikelikesbikes
Copy link
Contributor

This change drops support of go < 1.5. go1.4 has been officially unsupported since go1.6 was released 2016/02/17.

The PR was motivated by a bug I discovered, where req.RequestURI was returning "", so my router was failing to route on the escaped path.

Very open to thoughts and/feedback on how to proceed. Thanks!

This change drops support of go < 1.5. go1.5 has been officially
unsupported since go1.7 was released 2016/08/15.
@elithrar
Copy link
Contributor

elithrar commented Oct 18, 2017 via email

@kisielk
Copy link
Contributor

kisielk commented Oct 18, 2017 via email

@kisielk kisielk merged commit c9183aa into gorilla:master Oct 20, 2017
chrisdostert added a commit to chrisdostert/mux that referenced this pull request Nov 9, 2017
gorilla#306 changed UseEncodedPath to use native go encoded path handling so cautions in it's docs are no longer applicable.
elithrar pushed a commit that referenced this pull request Nov 9, 2017
#306 changed UseEncodedPath to use native go encoded path handling so cautions in it's docs are no longer applicable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants