-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
not handling escaped forward slashes properly #208
Comments
ORY Hydra had an API where you accept a parameter like The linked issue says "if [the] challenge is not properly escaped", but that's not true because it uses httprouter! Calling I don't use httprouter directly, but when Hydra announced the change and I checked that even with escaping it doesn't work I was quite surprised. RFC 3986: "When to Encode or Decode":
|
Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.13.0 to 1.14.0. - [Release notes](https://github.com/onsi/gomega/releases) - [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md) - [Commits](onsi/gomega@v1.13.0...v1.14.0) --- updated-dependencies: - dependency-name: github.com/onsi/gomega dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Hey there. Just found this issue:
Without an encoded forward slash, this works correctly:
But with an encoded forward slash, it does not.
I'm quite confident that the second example should have routed and the purchase-id parameters should be set to "3/4"
The text was updated successfully, but these errors were encountered: