You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Envoy's default upstream idle timeout is 1 hour. When the backend closes the connection in advance, it is easy to send a request when the connection is closed, causing problems such as 503.
Why do you need it?
Envoy's default upstream idle timeout is 1 hour. When the backend closes the connection in advance, it is easy to send a request when the connection is closed, causing problems such as 503.
How could it be?
global config:
envoyfilter :
Other related information
https://www.envoyproxy.io/docs/envoy/v1.20.3/api-v3/config/cluster/v3/cluster.proto
https://www.envoyproxy.io/docs/envoy/v1.20.3/api-v3/config/core/v3/protocol.proto#envoy-v3-api-msg-config-core-v3-httpprotocoloptions
The text was updated successfully, but these errors were encountered: