-
-
Notifications
You must be signed in to change notification settings - Fork 760
-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
Treats trailing slashes differently for swagger and normal endpoints #1884
Comments
Thanks @chbndrhnns, Not sure if this is inconsistent. If you change your example spec to (note the trailing slash after "paths": {
"/hello/": {
"get": { You get the same behaviour as the UI. I guess we could remove these two lines though so we use the raw path for the UI, which is configurable by the user: connexion/connexion/middleware/swagger_ui.py Line 130 in 211bdb0
connexion/connexion/middleware/swagger_ui.py Line 151 in 211bdb0
|
Thanks, you are right about the solution. there is a discussion about this on starlette side. I would want this to be configurable on. Objection side, as well. |
Description
/ui
returns a redirect and a call to/ui/
returns the swagger page/bla
returns the content and a call to/bla/
returns a redirectExpected behaviour
Consistent (and configurable) behaviour
Actual behaviour
Inconsistent
Steps to reproduce
Additional info:
Output of the commands:
The text was updated successfully, but these errors were encountered: