-
Notifications
You must be signed in to change notification settings - Fork 4.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
document idletimeout clearly #7420
Comments
Agreed it might be good to be clearer here. Something along the lines of https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/http/http_connection_management.html?highlight=timeout#timeouts would be good. |
+1 we have lots of different idle/stream timeouts and it would be good to do an overview of them and/or also have a FAQ. |
We'd appreciate clarification on how these stream-level timeouts affect HTTP 1 requests and connections, esp. what "stream reset" means in this context. |
Fixes envoyproxy/envoy#8190 Fixes envoyproxy/envoy#7420 Fixes envoyproxy/envoy#7331 Fixes envoyproxy/envoy#7312 Fixes envoyproxy/envoy#7284 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 8e0b240b0e0abcda07b7b259178bdad60a699019
As for me, when i looked the idletimeout at http connection manager 、route and also at cluster level。 There is a comment saying route level idletimeout will override http connection manager level. But what is the relation between cluster level and http connection manager level idletimeout .
The text was updated successfully, but these errors were encountered: