File paths with hash (#) marks in the directory names cause 404 error or empty dir in web UI
Created by: mkorich
We have the following directory in our repo that causes a 404 error in Gitlab when clicking into it from the web UI. http://gitlab.foo.com/dir/subdir#2
Whereas the following URL tweak would work: http://gitlab.foo.com/dir/subdir%232
Looks like a simple fix though to URL encode the path in the link.
Another side-effect I've seen is, when clicking into a "hash-malformed" url with gitlab is that the page is displayed as "empty" when there are, in fact, files in the dir. When clicking into a "hashed" dir like the one below, the display page for the dir appears empty (looks to be displaying the parent). http://gitlab.foo.com/stt/tree/dev/SystemTestingTool/automatonsPortal/100000042_Example#5 which displayed the following path only: stt / SystemTestingTool / automatonsPortal (note failure to click into the child directory)