Skip to content

Conversation

@antoniovleonti
Copy link
Contributor

Commit Message: ext_authz: perform request header checks progressively
Additional Description:

No behavior change. This pr just makes it so that the ext authz filter checks to make sure header limits (size, count) have not been violated as the mutations are added rather than once at the end. This prevents this filter from hogging the worker thread's time adding a bunch of headers when it will ultimately send a local reply.

Risk Level: low
Testing: unit tests updated for each case
Docs Changes: none necessary
Release Notes: none necessary (no externally visible behavior change)

Signed-off-by: antoniovleonti <[email protected]>
@antoniovleonti
Copy link
Contributor Author

/assign @tyxia

Copy link
Member

@tyxia tyxia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a high level question:

From description : This pr just makes it so that the ext authz filter checks to make sure header limits (size, count) have not been violated as the mutations are added rather than once at the end. Once this PR is merged, do we still need those validation/rejection at the end that you recently added?

If they are not needed, we should clean them up instead of having duplicated logics

@tyxia
Copy link
Member

tyxia commented Nov 2, 2025

/wait

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants