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.

Sign up for GitHub

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

Jump to bottom

handle URI encoded path components correctly #12

Open

nilclass opened this issue Jun 6, 2013 · 0 comments

Member

nilclass commented Jun 6, 2013

somewhere the path components get decoded and suddenly "foo/bar" is indistinguishable from "foo%2Fbar".
That is not good!

nilclass added a commit that referenced this issue


          (passing) spec to prove that I don't understand #12

56bc7a7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment