[Help] Problems with swagger-ui behind a reverse proxy.

[mustafamotiwala]

Hi,
I have a quarkus app running on say http://example.com/app. However that's behind a K8S Nginx Reverse proxy which maps /app to my quarkus app. However when I try to reach the swagger-ui at:
http://example.com/app/q/swagger-ui I get redirected to http://example.com/q/swagger-ui and the swagger-UI doesn't load.
I have in my application.properties

quarkus.swagger-ui.always-include=true

I have also tried mapping it to a different URL using:

quarkus.swagger-ui.always-include=true
quarkus.swagger-ui.path=/app/docs

But that also didn't work. I simply get a 404 from the quarkus app. If I however do:

quarkus.swagger-ui.always-include=true
quarkus.swagger-ui.path=/docs

And attempt to hit: http://example.com/app/docs - I am redirected to http://example.com/docs and then I get a 404 from the ingress nginx.

I am using Quarkus 3.8.1
Would appreciate any help to get this to work, or maybe this is a bug?

Thanks.

[quarkus-bot[bot]]

/cc @MikeEdgar (swagger-ui), @phillip-kruger (swagger-ui)

[phillip-kruger]

Are you setting the context root to app ?

quarkus.http.root-path=/app

[phillip-kruger]

Also look at https://quarkus.io/guides/management-interface-reference, this might / might no help

[cescoffier]

We do have 302 responses when we hit webjars. Is Swagger a webjar?

[phillip-kruger]

Yes it is, the only redirect there that I know about, is when we go from naked ( so root dir) to /index.html.

[mustafamotiwala]

So a few things to get this to work. Thanks @phillip-kruger - your answer clued me in on what is going on. What I found is if I hit the url: example.com/app/docs then I get a 302 and get redirected to example.com/docs/ - and that's where your comment clicked. The trailing /. If I hit example.com/app/docs/ - I get the swagger UI.

I then had to follow up and fix the URLs for the API using quarkus.smallrye-openapi.servers and setting it to %prod.quarkus.smallrye-openapi.servers=/app

Thanks once again @phillip-kruger & @cescoffier

[phillip-kruger]

Great !

[mustafamotiwala]

I know this closes the discussion, but do you think this could be considered a bug. i.e. shouldn't issue a 302-Redirect if the trailing / is missing?

[phillip-kruger]

@cescoffier ? W.d.y.t?

[siddharthapd]

this should be a bug IMHO. even the api docs its pointed to /q/openapi instead of /app/q/openapi. It should be automatically resolved using servers or some way !