Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #31176
Closed
Open
Issue created Aug 22, 2019 by Darva Satcher@dsatcherMaintainer

Make GitLab more robust through limiting the size of the wiki page

Goal

Make GitLab search more stable and robust against unintentional or intentional abuses and scenarios where "noisy neighbors" (users, projects, groups) are able to disrupt the wiki functionality by just doing one action.

Background

The Create Teams have been asked via Epic &1737, to proactively find application limits within the Knowledge code. The Knowledge Team identified limits in create-stage#39.

Solution

Application Limit Size of individual wiki page
What is the risk of not adopting this new limit? Wiki pages will be slow to load. Long-running ruby process (markdown) can be denial of service attack surface
Estimated Weight 1
Configurable/ Not Configurable Is Configurable
Are there existing limits? Yes/No
Include this in the implementation Should be configurable (critical for any existing users with large pages).
Edited Aug 23, 2019 by Darva Satcher
Assignee
Assign to
Time tracking