We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description:
Describe the desired behavior, what scenario it enables and how it
As a user, I'd like to increase the current defaults of these below settings for my setup Defaults are derived from https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#configuring-envoy-as-an-edge-proxy
initial_stream_window_size
initial_connection_window_size
[optional Relevant Links:]
Any extra documentation required to understand the issue.
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
@guydc does this fall into connection or a new http2 field within https://gateway.envoyproxy.io/latest/api/extension_types/#clienttrafficpolicyspec ?
connection
http2
I think that a new http2 field would be more appropriate.
discussed this in the meeting today, http2 seems like a popular option, will go with this in the init PR
zhaohuabing
No branches or pull requests
Description:
As a user, I'd like to increase the current defaults of these below settings for my setup
Defaults are derived from https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#configuring-envoy-as-an-edge-proxy
initial_stream_window_size
initial_connection_window_size
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: