From 51e21e040c65781cea10b54365e87fa8e0459737 Mon Sep 17 00:00:00 2001 From: James Moger <james.moger@gitblit.com> Date: Mon, 10 Oct 2011 19:12:00 -0400 Subject: [PATCH] Merge branch 'master' into rpc --- docs/03_faq.mkd | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/03_faq.mkd b/docs/03_faq.mkd index 12ceada..f690f26 100644 --- a/docs/03_faq.mkd +++ b/docs/03_faq.mkd @@ -36,12 +36,14 @@ ### Gitblit WAR will not authenticate any users?! Confirm that the <context-param> *realm.userService* value in your `web.xml` file actually points to a `users.properties` file. -### Gitblit won't open my grouped repository (/group/myrepo.git) or browse my branch/tag/ref?! -This is likely an url encoding/decoding problem related to your servlet container's security. There are two possible workarounds for this issue. In `gitblit.properties` or `web.xml`: +### Gitblit won't open my grouped repository (/group/myrepo.git) or browse my log/branch/tag/ref?! +This is likely an url encoding/decoding problem with forward slashes. There are two possible workarounds for this issue. In `gitblit.properties` or `web.xml`: 1. try setting *web.mountParameters* to *false*.<br/>This changes the url scheme from mounted (*/commit/myrepo.git/abcdef*) to parameterized (*/commit/?r=myrepo.git&h=abcdef*). 2. try changing *web.forwardSlashCharacter* to an asterisk or a **!** +Also, if you are running Gitblit behind a proxy, you must ensure that the proxy does not decode and then re-encode request urls with interpretation of *%2F*. If you are using Apache mod_proxy, specify [AllowEncodedSlashes NoDecode](http://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes). + ## General Interest Questions ### Gitblit? What kind of name is that? -- Gitblit v1.9.1