You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connexion 2 accepts both the URLS with or without trailing slashes when the connexion_app.app.url_map.strict_slashes = False. But this behaviour is no longer works in Connexion 3
Expected behaviour
It should accept both the URLS with or without trailing slashes when user call the API.
Actual behaviour
With the connexion upgrade to 3.0 it works bit differently. The request with backslash is responded with a 307 redirect response with the URL without trailing backslash in the response location header.
While I believe the current behavior is the correct default behavior, I would welcome a PR that re-adds a configuration option to disable the differentiation between paths with and without trailing slashes.
Description
Connexion 2 accepts both the URLS with or without trailing slashes when the
connexion_app.app.url_map.strict_slashes = False
. But this behaviour is no longer works in Connexion 3Expected behaviour
It should accept both the URLS with or without trailing slashes when user call the API.
Actual behaviour
With the connexion upgrade to 3.0 it works bit differently. The request with backslash is responded with a 307 redirect response with the URL without trailing backslash in the response location header.
Example
Response headers
Steps to reproduce
I have created a example application to reproduce the issue.
URL → https://github.com/hashannalaka/connexion-test.git
Additional info:
Output of the commands:
python --version
: Python 3.11.2pip show connexion | grep "^Version\:"
: Version: 3.0.0Is this the expected behavior in Connexion 3? I would appreciate any help regarding this.
The text was updated successfully, but these errors were encountered: