| | |
|---|
| | | http://192.168.1.2/log/myrepo.git/refs%2Fheads%2Fmaster
|
|---|
| | |
|
|---|
| | | **NOTE:**
|
|---|
| | | You can not trust the url in the address bar of your browser since your browser may *prettify* the url. When in doubt, *View Source* of the generated html to confirm the *href*.
|
|---|
| | | You can not trust the url in the address bar of your browser since your browser may decode it for presentation. When in doubt, *View Source* of the generated html to confirm the *href*.
|
|---|
| | |
|
|---|
| | | There are two possible workarounds for this issue. In `gitblit.properties` or `web.xml`:
|
|---|
| | |
|
|---|
| | |
|---|
| | |
|
|---|
| | | You must ensure that the proxy does not decode and then re-encode request urls with interpretation of forward-slashes (*%2F*). If your proxy layer does re-encode embedded forward-slashes then you may not be able to browse grouped repositories or logs, branches, and tags **unless** you set *web.mountParameters=false*.
|
|---|
| | |
|
|---|
| | | If you are using Apache mod_proxy, specify [AllowEncodedSlashes NoDecode](http://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes).
|
|---|
| | | If you are using Apache mod_proxy you may have luck with specifying [AllowEncodedSlashes NoDecode](http://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes).
|
|---|
| | |
|
|---|
| | | ### Running Gitblit on Tomcat
|
|---|
| | |
|
|---|
| | |
|---|
| | | You have a few options on how to handle this scenario:
|
|---|
| | |
|
|---|
| | | 1. [Tweak Tomcat](http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.10)
|
|---|
| | | Add *org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true* to *CATALINA_OPTS*
|
|---|
| | | Add *-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true* to *CATALINA_OPTS* or to your JVM launch parameters
|
|---|
| | | 2. *web.mountParameters = false* and use non-pretty, parameterized urls
|
|---|
| | | 3. *web.forwardSlashCharacter = !* which tells Gitblit to use **!** instead of **/**
|
|---|
| | |
|
|---|
| | |
|---|
| | | You might consider running [Gerrit](http://gerrit.googlecode.org) which does integrate [Apache Mina][mina] and supports SSH or you might consider serving [Git][git] on Linux which would offer real SSH support and also allow use of [many other compelling Git solutions](https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools).
|
|---|
| | |
|
|---|
| | | ### What types of Search does Gitblit support?
|
|---|
| | | Gitblit supports case-insensitive searches of *commit message* (default), *author*, and *committer*.<br/>
|
|---|
| | |
|
|---|
| | | As of 0.9.0, Gitblit supports Lucene-based searching.
|
|---|
| | |
|
|---|
| | | If Lucene indexing is disabled, Gitblit falls back to brute-force commit-traversal search. Commit-traversal search supports case-insensitive searching of *commit message* (default), *author*, and *committer*.<br/>
|
|---|
| | |
|
|---|
| | | To search by *author* or *committer* use the following syntax in the search box:
|
|---|
| | |
|
|---|
