Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2937

Closed
Open
Created Feb 07, 2013 by Administrator@rootOwner

Project names can conflict with route handling

Created by: justahero

If a project is created as admin with the name users in the global namespace it is not possible to log in or log out anymore, because of a resulting name conflict. It seems the authentication route /users gets masked by the project name. The application shows the project at /users but e.g. the user can not log out via /users/sign_out and gets a 404 error instead. A similar case is naming the project keys that creates the project but it's not possible to access it, in this case the route wins. This might not be such a relevant issue, but it can disable the access for others.

I searched for similar issues but only found #1894 (closed) so far where the project name "dashboard" is not allowed. I also tested other route-specific words like groups, projects, profile, admin but they behave fine and get rejected in the Rails app.

The latest head from the master branch was used. I try to write tests for this issue.

Assignee
Assign to
Time tracking