Skip to content
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

docs: clarify clusterClientRatelimit empty client id logic #2756

Conversation

AlexanderYastrebov
Copy link
Member

#0

Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
and can be changed with an optional fourth parameter.
The optional fourth parameter may specify comma-separated list of header names.
Skipper will join header values to obtain client identity.
If identity value is empty (i.e. when all header values are empty or missing) then ratelimit does not apply.
Copy link
Contributor

Choose a reason for hiding this comment

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

minor: maybe be describe what if some values are empty or missing, but it seems optional for user documentation.

Copy link
Member Author

Choose a reason for hiding this comment

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

All values must be missing/empty for the combined value to become empty (see TupleLookuper)

@RomanZavodskikh
Copy link
Contributor

👍

@RomanZavodskikh
Copy link
Contributor

BTW What does "#0" mean?

@MustafaSaber
Copy link
Member

👍

@AlexanderYastrebov AlexanderYastrebov merged commit f55a20a into master Nov 28, 2023
12 checks passed
@AlexanderYastrebov AlexanderYastrebov deleted the docs/reference/filters-clarify-clusterClientRatelimit-empty-value branch November 28, 2023 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants