Images cannot be seen on branches

[gitblit]

Originally reported on Google Code with ID 517

What steps will reproduce the problem?
1. have a Git repo with image files
2. branch it
3. navigate to the image file in the branch

What is the expected output? What do you see instead?
For the head I can see the image shown as the content of the file.
For the branch the server just sends back this string instead of the image data:

<h1>Error</h1><p>Sorry, the requested resource <strong>/documentation/docs/images/blah.png</strong>
was not found in <strong>johndoe/documentation</strong>.</p>

What version of the product are you using? On what operating system?
1.6.1 on Win7

Reported by bpalyi on 2014-10-22 18:13:58

[gitblit]

Oh, and the server log is:

RawServlet Failed to load reponame 65cf9edef95f7b7a082094ab3226d4deeba08b93 reponame/johndoe!documentation/documentation!docs!images!blah.png

Reported by bpalyi on 2014-10-22 18:17:16

[gitblit]

Go or WAR?
Are you navigating using the "tree" links with the full UI or are you navigating the
"raw" links?

Reported by James.Moger on 2014-10-22 18:54:46

[gitblit]

It's Go. And I'm navigating with the full UI, however I can see that at the end it's
the "raw" link that does not work...

Reported by bpalyi on 2014-10-22 19:00:56

[gitblit]

Oh, and where I detected all this was when I added an image to a Markdown file and wanted
to see it parsed: the image was not loading.

Reported by bpalyi on 2014-10-22 19:02:44

[gitblit]

I can't reproduce this.  Feel like creating a small example repo and attaching?

Reported by James.Moger on 2014-10-22 19:14:46

[gitblit]

I would, just have to finish up my documentation job first (currently my boss doesn't
really care about if the docs can be displayed in Gitblit, but I'd like to push the
thing ;-))

Reported by bpalyi on 2014-10-23 13:22:43

[flaix]

@bpalyi, any update on this?

[flaix]

The key here is that the branch name used was johndoe/documentation, which has a forward slash in it. Thus this is the problem of loading raw files from branches with a slash.
I am setting this as a duplicate of #1290, because that ticket has a better explanation in the report, unlike this one, even if this one was reported earlier.