-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
malformed authority error with HTTP2 and gRPC #525
Comments
Did you file an issue against the envoy HTTP proxy so they don't emit malformed authorities? |
Duplicate of #442 |
Unfortunately no 😞. I have fork h2 and just show a log warn if authority field parsing fail. I would be happy to merge this change in h2 but I do not know if this policy is the expected one by h2. |
I am not sure what you mean by "unfortunately no". Isn't Envoy a FOSS project? Personally I don't think a patch to allow completely malformed authorities should be accepted. |
Let's move this discussion to #442 please, as it is the same issue. |
I am running h2 as a service in k8s to process gRPC requests.
Some clients of my service (envoy HTTP proxy) got error responses du to invalid authority field:
I do not have any ability to change envoy behavior: it need to use HTTP2 + TLS + cannot change request headers and payload.
I agree this authority is a little bit unexpected...
Should we make this kind of Authority allowed ?
Is there any way to allow h2 processing the request even if
Authority::parse
failed ?The text was updated successfully, but these errors were encountered: