quarkus.http.root-path is applied to the management api as well

[FreifeldRoyi]

Describe the bug

As opposed to the documentation, when setting quarkus.http.root-path=aaaa, the management api /q needs to be prefixed with /aaaa/q

Expected behavior

management api would not be affected by the quarkus.http.root-path property. e.g:
quarkus.http.root-path=aaaa
management api --> /q

Actual behavior

/aaaa/q

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

java version "25" 2025-09-16 LTS Java(TM) SE Runtime Environment Oracle GraalVM 25+37.1 (build 25+37-LTS-jvmci-b01) Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 25+37.1 (build 25+37-LTS-jvmci-b01, mixed mode, sharing)

Quarkus version or git rev

3.30.1

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

Apache Maven 3.9.11

Additional information

No response

[geoand]

Are you sure about the property name? Asking because I don't see that property being used anywhere in Quarkus and when I do try to set it in a sample Quarkus application, I get:

WARN  [io.quarkus.config] (Quarkus Main Thread) Unrecognized configuration key "quarkus.http.resources" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

[FreifeldRoyi]

Oh my mistake..
i meant root-path. 🤦🏻‍♂️
I fixed the description

[geoand]

I could not reproduce the issue. Please provide a minimal reproducer so I can investigate further.

[FreifeldRoyi]

example.tar.gz

[geoand]

Thanks for the reproducer. Could you clarify why is not set? Without it, the management interface isn’t active, so the endpoints are served under the main HTTP root path rather than a separate management interface.