We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Source of the issue - https://github.com/anttiviljami/openapi-backend/blob/a3503fb8162169b3784755457a27788e0d0b613a/src/router.ts#L244
Actual behavior Currently, URLs like http://resource.co/somePath and http://resource.co//somePath (with an extra slash after .co) are treated as the same URLs by the OpenApiBackend router.
Expected behavior Triggering URLs with an extra slash should throw 404 if they are not described by swagger spec.
The text was updated successfully, but these errors were encountered:
agreed, PRs accepted
Sorry, something went wrong.
No branches or pull requests
Source of the issue - https://github.com/anttiviljami/openapi-backend/blob/a3503fb8162169b3784755457a27788e0d0b613a/src/router.ts#L244
Actual behavior
Currently, URLs like http://resource.co/somePath and http://resource.co//somePath (with an extra slash after .co) are treated as the same URLs by the OpenApiBackend router.
Expected behavior
Triggering URLs with an extra slash should throw 404 if they are not described by swagger spec.
The text was updated successfully, but these errors were encountered: