Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,059
    • Issues 1,059
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 53
    • Merge requests 53
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #4750
Closed
Open
Issue created Oct 01, 2019 by Mayra Cabrera@mayra-cabrera⚡Maintainer0 of 6 checklist items completed0/6 checklist items

Remove protected paths throttle from Omnibus

From %12.4, protected paths throttle is now handled by GitLab Rails (gitlab#29952 (closed)), making the Omnibus throttle deprecated (#4688 (closed), !3597 (merged)).

From the Omnibus Deprecation policy

For regular configuration, removal target should always be the date of the next major release.

The protected paths throttle is scheduled to be removed on %13.0

Backend plan

  • Remove rack_attack.rb.erb
  • Remove GitLabRails#parse_rack_attack_protected_paths
  • Remove Setting up paths to be protected by Rack Attack documentation
  • Remove Setting up throttling for ‘paths to be protected’ documentation
  • Remove it from attribute list
  • Remove the related specs
Edited Oct 01, 2019 by Mayra Cabrera
Assignee
Assign to
Time tracking