-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
http/1.1 protocol error: HPE_INVALID_METHOD #54016
Comments
This is because you are only overriding the Host header, not the SNI (TLS) name. |
excuse me pls; wrong sentence; correcting: |
Sorry, I didn't understand, what do you mean? I've used;
|
Actually, I have no purpose like "to override" or "not to override". Should I preserve the header? How can do it or how can I set it? Could you please advise?
|
I tried |
Further logs:
|
Is this the right place to submit this?
Bug Description
Hello,
I am trying to implement secure istio gateway. The traffic will access to istio-ingress gateway through ALB. My configs are below:
my AWS ALB Ingress Config:
I create certs:
Some checks:
When I attempt to access app from outside of the cluster I get 502 bad gateway error.
When I attempt to access app from inside of the cluster I get 404 bad gateway error.
Could you please advise what I am missing?
Thanks&Regards
Version
Additional Information
istiod namespace> istio-system
istio-gateway > istio-ingress
istioctl analyze -n demoapps
doesn't find any problems.My loadbalancer healthchecks are ok.
My istio ingress gateway uses "NodePort" service.
When I try the same architecture by using nginx ingress controller (without tls), it works.
My EKS has following rules:
My istio-ingressgateway produces the following errors:
The text was updated successfully, but these errors were encountered: