-
Notifications
You must be signed in to change notification settings - Fork 681
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
Is is possible to "disable_on_etag_header: true" to envoy compressor extension #4679
Comments
could you add a little more detail to the description on why this feature is useful to you? just for context for anyone picking this up and to add some justification seems reasonable as a feature to add see here where we configure the compressor filter: contour/internal/envoy/v3/listener.go Lines 251 to 277 in 491e263
we will likely have to add this feature as a global configuration, since the compressor filter is per Envoy HTTPConnectionManager and for HTTP virtualhosts there is only one (though there are many filter chains for HTTPS virtualhosts) the global flag will probably go somewhere here:
let us know if you are willing to contribute, PRs are welcome! otherwise we will get this in the backlog and prioritized |
thanks for the reply |
you can disable compression if your response content-type is not in this set: contour/internal/envoy/v3/listener.go Lines 272 to 281 in 602a77f
see envoy field documentation: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/compressor/v3/compressor.proto#envoy-v3-api-field-extensions-filters-http-compressor-v3-compressor-content-type |
xref #6511 |
Can I pass
disable_on_etag_header: true
to envoy; preferably by HTTPProxy route; but envoy as whole would be acceptable.Searched docs from both contour and envoy and haven't had much luck.
Thanks
Environment:
kubectl version
): v1.21.14-eks-18ef993The text was updated successfully, but these errors were encountered: