envoyproxy/gateway

Option to enable envoy request or response headers separately

Open

#8522 aperta il 13 mar 2026

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Go (802 fork)auto 404
area/apihelp wanted

Metriche repository

Star
 (2871 star)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

Description:

Describe the desired behavior, what scenario it enables and how it would be used.

I would like to be able to enable envoy request headers like x-envoy-original-path so that I see the original path for URL rewritten requests in traces and access logs. There is an option in CTP called enableEnvoyHeaders which does this. However, this also enables envoy response headers which I do not want to return to clients.

Would it be possible to have separate flags in CTP for enabling request or response headers?

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Previous discussion here for context: https://github.com/envoyproxy/gateway/issues/8477#issuecomment-4050988146

Guida contributor