envoyproxy/envoy

gzip: Be able to only compress external responses

Open

#10,310 opened on Mar 9, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/compressionhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

gzip: Be able to only compress external responses

Description: Since gzip is pretty computationally heavy, it would be great if envoy had the option to only gzip responses that will be external. We don't want to gzip at the front proxy layer, as our front proxy is CPU sensitive. But it would be great if we can compress just one hop over at the sidecar of edge services.

Ideally, this means if a request has the header x-envoy-external-address, the sidecar will compress the response.

Contributor guide

Research direction
Implement a new gzip filter configuration option that allows enabling compression only when a specific header (e.g., x envoy external address) is present in the request. This would involve modifying the existing gzip filter or creating a new filter that wraps the gzip logic and conditionally applies it.
Tech stack
cpp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoy proxy knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30