the topic is a tad misleading i guess, but i did not know how to describe better in a subject. I am running gitblit go on ubuntu, and so far it seems to run smooth and nice except for one thing. I can click the view/diff/blame links on the summary page just fine. If i click view, and then on any of the view/diff/blame links in the commit view's "changed files" area i get a 404. The ones in the tweak area work fine on the same page.
> the topic is a tad misleading i guess, but i did not know how to describe
> better in a subject. I am running gitblit go on ubuntu, and so far it seems
> to run smooth and nice except for one thing.
> I can click the view/diff/blame links on the summary page just fine. If i
> click view, and then on any of the view/diff/blame links in the commit
> view's "changed files" area i get a 404. The ones in
> the tweak area work fine on the same page.
On Tuesday, June 19, 2012 1:43:52 PM UTC+2, James Moger wrote:
> Hmmm. That is weird. Are you running GO behind a proxy? Can you > compare the links for a working diff and a broken diff?
> I'm not sure what "tweak area" means.
> -J
> On Tue, Jun 19, 2012 at 3:03 AM, Thorsten Kaufmann > <instinct...@googlemail.com> wrote: > > Hey there,
> > the topic is a tad misleading i guess, but i did not know how to > describe > > better in a subject. I am running gitblit go on ubuntu, and so far it > seems > > to run smooth and nice except for one thing. > > I can click the view/diff/blame links on the summary page just fine. If > i > > click view, and then on any of the view/diff/blame links in the commit > > view's "changed files" area i get a 404. The ones in > > the tweak area work fine on the same page.
Wicket (the web framework used by Gitblit) replaces forward-slashes in
parameters with %2F. It has to do this because it uses
forward-slashes to delimit parameters in mounted/pretty urls.
Some proxy's really do not like %2F encoded values and they re-encode
those as / before forwarding on to Gitblit. This breaks
Wicket/Gitblit. When you are running behind a proxy you have to take
an extra step or two to make sure your urls work properly.
For example the demo site runs on a JBoss instance behind one of
RedHat's proxy servers. The demo uses web.forwardSlashCharacter = !
to get around proxy server interference.
On Tuesday, June 19, 2012 3:04:14 PM UTC+2, James Moger wrote:
> Wicket (the web framework used by Gitblit) replaces forward-slashes in > parameters with %2F. It has to do this because it uses > forward-slashes to delimit parameters in mounted/pretty urls.
> if param2 had a a '/' in it then Wicket will not be able to identify > param3. So Wicket replaces the '/' with %2F so the url will be: > http://localhost/param1/my%2Fparam%2F2/param3
> Some proxy's really do not like %2F encoded values and they re-encode > those as / before forwarding on to Gitblit. This breaks > Wicket/Gitblit. When you are running behind a proxy you have to take > an extra step or two to make sure your urls work properly.
> For example the demo site runs on a JBoss instance behind one of > RedHat's proxy servers. The demo uses web.forwardSlashCharacter = ! > to get around proxy server interference.
> So it also seems to work for other repos. I got no idea how that might > happen tho.
> Regards, > Thorsten
> On Tuesday, June 19, 2012 3:04:14 PM UTC+2, James Moger wrote:
>> Wicket (the web framework used by Gitblit) replaces forward-slashes in >> parameters with %2F. It has to do this because it uses >> forward-slashes to delimit parameters in mounted/pretty urls.
>> if param2 had a a '/' in it then Wicket will not be able to identify >> param3. So Wicket replaces the '/' with %2F so the url will be: >> http://localhost/param1/my%2Fparam%2F2/param3
>> Some proxy's really do not like %2F encoded values and they re-encode >> those as / before forwarding on to Gitblit. This breaks >> Wicket/Gitblit. When you are running behind a proxy you have to take >> an extra step or two to make sure your urls work properly.
>> For example the demo site runs on a JBoss instance behind one of >> RedHat's proxy servers. The demo uses web.forwardSlashCharacter = ! >> to get around proxy server interference.
