Skip to content

429 rate limit responses carry no security headers #1851

Open

Description

@Wikid82

Observed while verifying docs for #1774 (PR #1849): the 429 from the proxy rate limiter has an empty body and none of the usual response headers (HSTS, X-Frame-Options, X-Content-Type-Options). Severity: low. Suggested: check whether the handler order puts the limiter before the headers handler and, if so, whether the headers should apply to its responses.

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

Metadata

Metadata

Assignees

Labels

securitySecurity-related

Projects

  • Status
    Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions