Quarkus SwaggerUI ignores http.root.path if quarkus.resteasy-reactive.path is set

[Fernichter]

trafficstars

Describe the bug

Im using the following config:

quarkus.http.root-path=/test-service
quarkus.http.port=${PORT:8080}
quarkus.resteasy-reactive.path=rest

SwaggerUI converts this to the following URL in the "try-out" feature:

curl -X 'GET' \
  'http://localhost:8080/rest/test' \
  -H 'accept: application/json'

SwaggerUI seems to ignore the http.root.path set in the config.

When im using the @ApplicationPath("/rest") annotation instead of quarkus.resteasy-reactive.path, everything works just fine. Is this intended or am I missing something?

Thanks

Expected behavior

SwaggerUI should provide the following request-url:

curl -X 'GET' \
  'http://localhost:8080/test-service/rest/test' \
  -H 'accept: application/json'

Actual behavior

SwaggerUI provides the following request-url:

curl -X 'GET' \
  'http://localhost:8080/rest/test' \
  -H 'accept: application/json'

How to Reproduce?

Use the following config:

quarkus.http.root-path=/test-service quarkus.http.port=${PORT:8080} quarkus.resteasy-reactive.path=rest

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

Quarkus 2.10.2.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot[bot]]

/cc @FroMage, @MikeEdgar, @geoand, @phillip-kruger, @stuartwdouglas

[Fernichter]

Can anyone reproduce this bug?

[phillip-kruger]

I have not looked at this yet. If you create a small reproducer that makes it easier

[yacine-1]

Hi,

I also have this problem with the same findings. I defined my root path like this: quarkus.http.root-path=/myApp

And I have an application that works well with the old version of RESTEasy with quarkus.resteasy.path=/api Swagger requesting: http://localhost:8080/myApp/api/resource ✔️

But now I have this problem with Swagger on my new application which uses quarkus.resteasy-reactive.path=/api Swagger requesting: http://localhost:8080/ ~~myApp~~ /api/resource ❌ (http://localhost:8080/api/resource)

Swagger makes requests without considering quarkus.http.root-path when quarkus.resteasy-reactive.path is also defined at the same time. I worked around this problem temporarily by deleting resteasy-reactive.path.

[phillip-kruger]

@MikeEdgar ^^^

[MikeEdgar]

The issue is that for RESTEasy Classic the smallrye-openapi extension uses the RESTEasy extension's path that already includes the http.root-path, whereas for reactive it's using the raw configuration property. I'll put together a PR to address this.

https://github.com/quarkusio/quarkus/blob/d21383094cdc29d3d7370d6eb40fef923f2663be/extensions/smallrye-openapi/deployment/src/main/java/io/quarkus/smallrye/openapi/deployment/SmallRyeOpenApiProcessor.java#L869-L883