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
Multiple services in our system that depend on either netty client or web client see an intermittent failure related to the illegal character in authority at index 21 without much information on any possible illegal character in the URL as printed in stack trace
Caused by: java.net.URISyntaxException: Illegal character in authority at index 21: http://localhost:8080/req/path
at java.base/java.net.URI$Parser.fail(Unknown Source)
at java.base/java.net.URI$Parser.parseAuthority(Unknown Source)
at java.base/java.net.URI$Parser.parseHierarchical(Unknown Source)
at java.base/java.net.URI$Parser.parse(Unknown Source)
at java.base/java.net.URI.<init>(Unknown Source)
at java.base/java.net.URI.create(Unknown Source)
at reactor.netty.http.HttpOperations.resolvePath(HttpOperations.java:416)
the index 21 is next char after the port, the static string added in HttpOperations:419
from the stack, we don't see any illegal char at index 21, it's very intermittent, and not able to reproduce any thoughts on this. can it be any character that may be added internally by the netty client that's not visible in logs as many services have the same exception at the same index?
The text was updated successfully, but these errors were encountered:
@AkashB23 You don't specify the Reactor Netty version, so I will comment on the latest version of HttpOperations
the index 21 is next char after the port, the static string added in HttpOperations:419
If this is the suspicious row then you can see that it is guarded by if (tempUri.charAt(0) == '/') {, so I don't see how something can be added in addition to what we have, the next call is URI.create
Multiple services in our system that depend on either netty client or web client see an
intermittent failure related to the illegal character in authority at index 21
without much information on any possible illegal character in the URL as printed in stack tracethe index 21 is next char after the port, the static string added in HttpOperations:419
from the stack, we don't see any illegal char at index 21, it's very intermittent, and not able to reproduce any thoughts on this. can it be any character that may be added internally by the netty client that's not visible in logs as many services have the same exception at the same index?
The text was updated successfully, but these errors were encountered: