Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !1747

Merged
Created Feb 26, 2025 by Jérome Perrin@jeromeOwner

stack/erp5: rate limit clients on backend haproxy

  • Overview 12
  • Commits 1
  • Pipelines 3
  • Changes 5

This supports defining rate limits as maximum number of matched requests over a period of time for the same client IP.

Requests are matched either by a regular expression on URL path or a response status code.

Once a client exceeded the rate limit, haproxy will reply with HTTP status code 429 ("Too Many Requests") until the expiration period configured on the rule has passed. Optionally, the responses can be made after the "tarpit" delay.

Edited Apr 16, 2025 by Jérome Perrin
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: feat/erp5-haproxy-rate-limit
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7