You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Helidon WebClient uses an absolute request URI rather than a relative one when submitting HTTP requests. Most of times this is not an issue, but there are some HTTP server implementation that are not able to deal with it.
For example, due to this issue using Helidon WebClient I'm not able to get an OAuth Token from Oracle Identity Cloud because my requests fail with a 404.
The requests issued by Helidon WebClient look like the following:
Section 5 of RFC 2116 is a bit ambiguous about the Request-URI format responsibilities:
To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers MUST accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
To avoid such kind of issues, the Helidon WebClient should used absolute URI only when effectively required, or make this behavior configurable.
Steps to reproduce
To verify the Request-URI format used by the Helidon Web Client, just enable the logging at finest level to see the request issued towards the HTTP server
The text was updated successfully, but these errors were encountered:
Environment Details
Problem Description
Helidon WebClient uses an absolute request URI rather than a relative one when submitting HTTP requests. Most of times this is not an issue, but there are some HTTP server implementation that are not able to deal with it.
For example, due to this issue using Helidon WebClient I'm not able to get an OAuth Token from Oracle Identity Cloud because my requests fail with a 404.
The requests issued by Helidon WebClient look like the following:
While instead the expected format should be:
Section 5 of RFC 2116 is a bit ambiguous about the Request-URI format responsibilities:
To avoid such kind of issues, the Helidon WebClient should used absolute URI only when effectively required, or make this behavior configurable.
Steps to reproduce
To verify the Request-URI format used by the Helidon Web Client, just enable the logging at finest level to see the request issued towards the HTTP server
The text was updated successfully, but these errors were encountered: