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
The HttpConnectionManager.request_timeout is documented as:
A timeout for idle requests managed by the connection manager. The timer is activated when the request is initiated, and is disarmed when the last byte of the request is sent upstream (i.e. all decoding filters have processed the request), OR when the response is initiated.
The second sentence describes an active request, but the first sentence says this is a timer for "idle requests". Maybe this language can be clarified?
Relevant Links:
Any extra documentation required to understand the issue.
The documentation for the HTTP connection manager `request_timeout`
says it is a timeout for idle requests, but it is actually the time
to receive a complete request from the downstream client.
This fixesenvoyproxy#10481.
Signed-off-by: James Peach <jpeach@apache.org>
The documentation for the HTTP connection manager `request_timeout`
says it is a timeout for idle requests, but it is actually the time
to receive a complete request from the downstream client.
This fixes#10481.
Signed-off-by: James Peach <jpeach@apache.org>
Description:
The
HttpConnectionManager.request_timeout
is documented as:The second sentence describes an active request, but the first sentence says this is a timer for "idle requests". Maybe this language can be clarified?
Relevant Links:
https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/filter/network/http_connection_manager/v2/http_connection_manager.proto.html
The text was updated successfully, but these errors were encountered: