Skip to content

fix(infra): retire la priorité explicite qui désactivait le rate-limit login #28

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.

Sign up for GitHub

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

Merged
gilmry merged 1 commit into from
Aug 20, 2026
Merged

fix(infra): retire la priorité explicite qui désactivait le rate-limit login #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,13 @@ services:
- "traefik.http.routers.elevia-backend-login.entrypoints=websecure"
- "traefik.http.routers.elevia-backend-login.tls.certresolver=letsencrypt"
- "traefik.http.routers.elevia-backend-login.service=elevia-backend"
- "traefik.http.routers.elevia-backend-login.priority=10"
# No explicit priority: Traefik ranks routers by matcher length when
# priority isn't set, and this rule is already longer/more specific
# than the catch-all elevia-backend router, so it wins on its own.
# An earlier explicit "priority=10" here was *lower* than the
# catch-all's auto-computed priority, so the catch-all matched first
# and silently bypassed the rate limit for every request - verified
# live in prod (15 rapid /auth/login calls, zero 429s).
- "traefik.http.routers.elevia-backend-login.middlewares=elevia-login-ratelimit"
- "traefik.http.middlewares.elevia-login-ratelimit.ratelimit.average=5"
- "traefik.http.middlewares.elevia-login-ratelimit.ratelimit.period=1m"
Expand Down
Loading