-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
tcp tunneling: optionally move response header to downstream info #23118
Changes from 8 commits
39dd246
13ea62d
0d78ac4
50ac8a6
38b492a
de40f8d
9ed361b
a5b05f3
ba86a92
f109cfd
0cfe94c
2cb76ea
b557893
826cb13
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -99,6 +99,10 @@ message TcpProxy { | |
// Neither ``:-prefixed`` pseudo-headers nor the Host: header can be overridden. | ||
repeated config.core.v3.HeaderValueOption headers_to_add = 3 | ||
[(validate.rules).repeated = {max_items: 1000}]; | ||
|
||
// Emit response headers to the downstream info filter state for consumption | ||
// by the network filters. The filter state key is ``envoy.tcp_proxy.tunnel_response_headers``. | ||
bool emit_response_headers = 4; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd lean towards something akin to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @markdroth For API review and deciding on naming. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about calling this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Renamed. |
||
} | ||
|
||
message OnDemand { | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -206,6 +206,11 @@ new_features: | |
- area: redis | ||
change: | | ||
added support for quit command to the redis proxy. | ||
- area: tcp_proxy | ||
change: | | ||
added support for emitting the response headers in :ref:`TunnelingConfig | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. emitting -> propagating ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. |
||
<envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.TunnelingConfig.emit_response_headers>` to | ||
the downstream info filter state. | ||
|
||
deprecated: | ||
- area: http | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe make the key propagate as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.