-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Envoy seems not to honor "Connection: close" HTTP header #234
Labels
Comments
Thanks for the report will fix |
fixed |
👏 |
rshriram
pushed a commit
to rshriram/envoy
that referenced
this issue
Oct 30, 2018
Automatic merge from submit-queue. [DO NOT MERGE] Auto PR to update dependencies of mixerclient This PR will be merged automatically once checks are successful. ```release-note none ```
PiotrSikora
pushed a commit
to PiotrSikora/envoy
that referenced
this issue
Aug 5, 2020
…envoyproxy#11831) (envoyproxy#234) Currently Opencensus tracer uses grpcService proto to configure its tracing client stub. It uses GoogleGrpcUtil to construct a channel and create client stub with that. However, the channel created there does not take care of initial_metadata from grpcService configure. This change fills in OCprepare_client_context option in export to make it respect initial metadata. Risk level: Low Signed-off-by: Pengyuan Bian <[email protected]>
wolfguoliang
pushed a commit
to wolfguoliang/envoy
that referenced
this issue
Jan 23, 2021
fix docs/root/install/building.rst translation issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a setup when we have to varnish an Envoy-fronted server, and have defined Varnish probes to test the backend health. The problem is that Varnish considers the backend to be perpetually sick because it does not close the connection after forwarding the response, even if the probe sends the
Connection: close
header.Here is a network capture from a probe being sent:
Varnish is sending
Connection: close
but Envoy is not closing the connection after sending its response. Varnish is closing the connection itself after 3 seconds, but that causes it to consider the probe failing and reject the backend.The text was updated successfully, but these errors were encountered: