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

Closed
Open
Created Jun 24, 2014 by Administrator@rootOwner

I get a 404 for each PATCH request I try to make

Created by: whatyouhide

I get a 404 error for each PATCH request I try to make:

ActionController::RoutingError (No route matches [PATCH] "/websites/sitename/merge_requests/5/edit")

I'm an admin of our GitLab instance, I'm 100% sure I have all the right permissions and so on; anyways it happens both when dealing with group projects (where I own the group) as well as with personal projects. I really don't know where this is coming from, since it started happening out of the blue apparently.

It happens with GitLab CI too. We're on GitLab 7.0.0 (but it happened with 6.9 too).

Edit

Here comes the fun. This error only shows up in Chrome (Canary 38) on OSX. Every form I encountered in GitLab has POST as its action, and the "Network" tab in the Chrome DevTools shows it issues a POST request to the url specified in the action.

Still, it returns me a 404 and the error mentioned above (which mentions a PATCH request I never issue).

Everything works in Safari for example.

Assignee
Assign to
Time tracking