Closed nabeelio closed 5 years ago
In my case, the HTTP/1.0 requests are health checks issued by digitaloceans loadbalancer. We need to be able to say "OK" to these health checks, or the service will be marked as DOWN.
@daimoniac It looks like http/1.0 is supported, but it needs explicit configuration: https://github.com/envoyproxy/envoy/blob/02b2e798593ecebc48ef7c4a4f1832d5e533498d/source/common/http/conn_manager_impl.cc#L568
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.
Hi all, I'm having a strange issue. I'm running Ambassador with Envoy, and there are intermittent 426 errors returned. I'm not quite sure what to make of it. I'm using an Azure internal load balancer, which is on a static IP.
The endpoint is
/api/v1/gateway
, which just returns a 200, and a JSON string. Nothing fancy.I did see that @huxiaobabaer had a similar issue, but it was closed. Here's some requests:
However,
tcpdump
shows:And I've started getting this in my browser as well:
And the corresponding Envoy log:
The odd part is that when I restart Envoy, it behaves for a little bit. I'm running tcpdump in the same container that Envoy is running in.
Running a
kubectl port-forward ...
to bypass Envoy works fine. So I'm not sure where thisHTTP/1.0
downgrade is coming from and I'm not sure where to go from here. Looking through the Envoy source, I only see one instance of where this response is sent.I've attached some of the stats/logs. I couldn't run the collector - when I restart it, it's intermittent so I'm not sure how large the logs would get - it's also running in a container
Now, I know this is an older version of Envoy, I can try upgrading to the latest Ambassador EA 5, but I'm not able to do that at the moment.
Thanks for the help!
diag.txt