Non-standard proxy forwarded headers are not being parsed

Describe the bug

Non-standard proxy forwarded headers are not being parsed, even though both standard and non-standard forwarded headers configurations are enabled. This behavior contradicts information at https://quarkus.io/guides/vertx#running-behind-a-reverse-proxy.

The corresponding implementation at ForwardedParser.java shows that it will not parse non-standard headers when allowForwarded config is enabled.

Expected behavior

It should work as stated in the documentation

Both configurations related with standard and non-standard headers can be combine. In this case, the Forwarded header will have precedence in presence of both set of headers.

Actual behavior

With both configurations enabled, quarkus server did not parse non-standard header from request.

Configuration

# Add your application.properties here, if applicable.
quarkus:
  http:
    proxy:
      proxy-address-forwarding: true
      allow-forwarded: true
      enable-forwarded-host: true
      enable-forwarded-prefix: true

[alsasian]

@ejba thanks for the clarification. Indeed, I was expecting some kind of failover mechanism to parse custom header when standard header is not provided. I was not sure whether the issue is with the doc or the implementation.

Thanks again for checking 👍.

[ejba]

@alsasian I am the one shall say thanks here! 😉