feat(api): add addIfAbsent header action in ClientTrafficPolicy #7978
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Feature - adds new API field and functionality
What this PR does / why we need it:
This PR adds support for the
addIfAbsentheader action inHTTPHeaderFilter, which adds headers only if they don't already exist. This maps to Envoy'sADD_IF_ABSENTaction.Use Case:
Set default headers (e.g.,
Content-Security-Policy,X-Frame-Options) at the gateway level that can be overridden by backend responses. Unlikeaddwhich appends to existing headers, orsetwhich overwrites them,addIfAbsentis a no-op if the header is already present.Changes:
AddIfAbsentfield toHTTPHeaderFilterinapi/v1alpha1/shared_types.goAddIfAbsentfield to IRAddHeaderstruct ininternal/ir/xds.gotranslateHeaderModifier()ininternal/gatewayapi/clienttrafficpolicy.gobuildXdsAddedHeaders()ininternal/xds/translator/route.gobuildHeaderMutationRules()ininternal/xds/translator/header_mutation.gosite/content/en/latest/tasks/traffic/http-response-headers.mdExample usage:
Which issue(s) this PR fixes:
Fixes #7656
Release Notes: Yes