-
Notifications
You must be signed in to change notification settings - Fork 23
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
Get enable_x_ratelimit_headers: DRAFT_VERSION_03
to work
#156
Labels
Comments
chirino
added a commit
to chirino/limitador
that referenced
this issue
Mar 19, 2023
chirino
added a commit
to chirino/limitador
that referenced
this issue
Mar 20, 2023
chirino
added a commit
to chirino/limitador
that referenced
this issue
Mar 20, 2023
chirino
added a commit
to chirino/limitador
that referenced
this issue
Mar 20, 2023
chirino
added a commit
to chirino/limitador
that referenced
this issue
Mar 21, 2023
alexsnaps
added
kind/enhancement
New feature or request
area/server
size/medium
target/current
labels
Apr 13, 2023
Not tested by QE currently. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I tried setting the enable_x_ratelimit_headers option in the envoy rate limiting filter. But the expected headers were not set in the response.
the filter's configuration looks like:
The only header I see in the responses is
x-envoy-ratelimited: true
, I was hoping to get headers likeX-RateLimit-Limit: 10, 10;w=1;name="per-ip", 1000;w=3600
Tasks
The text was updated successfully, but these errors were encountered: