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

Closed
Open
Created Jan 17, 2013 by Administrator@rootOwner

404 when trying to view content inside of a 'files/' directory

Created by: mckern

I've got a stock 4.0.1 instance set up (fresh, not upgraded), and when attempting to browse through one of my projects, I receive a 404 if I try to browse content under a directory named 'files/'. Here's the associated error log from production.log

Started GET "/mckern/automated-it-infrastructure-management/tree/master/puppet/files?_=1358439874294" for 127.0.0.1 at 2013-01-17 11:24:31 -0500
Processing by ProjectsController#files as JS
  Parameters: {"_"=>"1358439874294", "id"=>"mckern/automated-it-infrastructure-management/tree/master/puppet"}
  Rendered public/404.html (0.5ms)
Filter chain halted as :project rendered or redirected
Completed 404 Not Found in 14ms (Views: 10.0ms | ActiveRecord: 0.6ms)

And here's what I see in the browser:

Topor

I've confirmed behavior across multiple repos, and on a separate system. I'm happy to dig into this, but I wanted to get the bug opened up before I start fiddling with anything.

Assignee
Assign to
Time tracking