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

Add config flag to hide X-RateLimit- headers on response #2172

Open
1 task done
SleepyMorpheus opened this issue Nov 20, 2024 · 0 comments
Open
1 task done

Add config flag to hide X-RateLimit- headers on response #2172

SleepyMorpheus opened this issue Nov 20, 2024 · 0 comments

Comments

@SleepyMorpheus
Copy link

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe it

Throttler response with both global and local rate-limiting usages as headers after a request. We don't want to expose our rate limiting settings to users.

Describe the solution you'd like

Add a config flag to the interface (like hideHeaders) that prevents the headers from being exposed.

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

It does not always make sense to expose the internal state of our application to the user. True, we could remove the headers again, but having a flag is the cleaner way.

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

No branches or pull requests

1 participant