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
  • #2793

Closed
Open
Created Jan 28, 2013 by Administrator@rootOwner

Using v3 API to access namespaced project results in 404

Created by: jgoldschrafe

While the v3 API works great for me in accessing projects with no namespace (e.g. api/v3/projects/myproject), it doesn't work at all for accessing projects with a namespace in their prefix (e.g. api/v3/projects/myname/myproject -- the Grape router appears to break :id at the forward slash, causing the API call to return a 404 even though the resource is quite valid.

Changing the resource calls to insert requirements: { id: /[a-zA-Z.0-9_\-\/]+/ } to suppress breaking on / characters, as the application route does, appears to resolve this issue, but I don't know Grape well enough to figure out what the idiomatic way is to make this change across the whole API codebase.

Assignee
Assign to
Time tracking