-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Illegal character in authority at index 21 #3662
Comments
@AkashB23 You don't specify the Reactor Netty version, so I will comment on the latest version of
If this is the suspicious row then you can see that it is guarded by reactor-netty/reactor-netty-http/src/main/java/reactor/netty/http/HttpOperations.java Lines 415 to 420 in abf21e6
|
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
yes exactly, thats the confusion here since the error specified failed authority validation which is just a string added at the line specified, how can it be failing with illegal char at 21 |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
We can receive the full URI in the format "http://localhost:8080/", in this case we will not do any transformation and will try to parse it with You can extend the Reactor Netty pipeline and add a custom ChannelHandler where you can inspect the URI before it reaches Reactor Netty 's |
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: