`quarkus.http.redirect-to-non-application-root-path` is not working on master branch

Given an application with the following configuration:

quarkus.http.root-path=/api
quarkus.http.non-application-root-path=/q
quarkus.http.redirect-to-non-application-root-path=true

An http://localhost:8080/openapi should return an HTTP 301 with a location header /q/openapi but is returning a 404.

Looks like on master we are pre-pending quarkus.http.root-path. master -> http://localhost:8080/api/health -> redirected to http://localhost:8080/q/health previous -> http://localhost:8080/health -> redirected to http://localhost:8080/q/health>

[rsvoboda]

Maybe this blog post could be transformed into regular Quarkus guide to summarize available non application endpoints, their paths and configuration options.

New blog posts are coming and path-resolution-in-quarkus one will be moved to “Older posts” sooner or later. Once that happens Quarkus users will have harder time to find the info. Another benefit of regular guide is that the text is present in the main Quarkus codebase and it is easier to find the content with offline google search, I mean git grep.

[kenfinnigan]

That’s correct behavior.

All endpoints came off the http.root-path, so the redirects do the same. If http.root-path is something other than / the redirects will come off the path it defines