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
swagger-ui change URL #887
Comments
hey @czchen, Can you please provide the This may be caused by a trailing-slash redirect. Can you try https://example.com/v0/ui/ (with trailing slash) and let me know if you are still having the issue? I think the issue may also fixed by #823 - the goal of that diff is to fix connexion behavior when behind a reverse-proxy. |
|
ok, thanks for the info.
Are you using aiohttp or flask?
…On Wed, Feb 27, 2019, 1:58 AM ChangZhuo Chen (陳昌倬) ***@***.***> wrote:
- The servers block is:
servers:
- url: /v0
- I don't set base_path
- https://example.com/v0/ui/ does not have this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#887 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAlPScaHxA6Pndz__Fl2gtXQYfrTcxlAks5vRUt4gaJpZM4bPWRO>
.
|
flask |
My guess is that Can you include the output of a verbose
But I would expect the redirected url to include the trailing slash like so:
Also if you have time, can you try out #823 and see if that fixes your issue? |
The following is output of `curl --verbose http://exampke.com/v0/ui. ps. We change our auth sidecar from keycloak-gatekeeper to nginx, the redirect URL is also changed.
|
I think this may be related to your nginx configuration. I wasn't able to reproduce your issue.
After this I tried to access the ui without the trailing slash, and the redirect looks correct to me:
|
I've changed the ticket type to |
Description
We put our connexion application in k8s. But when we access swagger-ui via https://example.com/v0/ui, it is redirected to http://127.0.0.1:5000/v0/ui so we cannot use swagger UI. All other URLs in example.com are not redirected, so we think the problem is in swagger-ui.
Expected behaviour
When access https://example.com/v0/ui, we shall be about to access swagger-ui
Actual behaviour
When access https://example.com/v0/ui, we are redirected to http://127.0.0.1:5000/v0/ui.
Steps to reproduce
Additional info:
Output of the commands:
python --version
$ python --version
Python 3.7.2+
pip show connexion | grep "^Version\:"
$ pip show connexion | grep "^Version:"
Version: 2.2.0
The text was updated successfully, but these errors were encountered: