summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGlenn Matthys <glenn@webmind.be>2016-01-17 23:15:53 +0100
committerGlenn Matthys <glenn@webmind.be>2016-01-17 23:15:53 +0100
commit0d32645ba2eafb1abfdb85bbe358d4db5e929aba (patch)
tree80d3f7d09adaa71be19a62670832505683528265
parent7e5107ef3e2bb0d7c31d3050fb8ba6cc1601ef1a (diff)
downloadgitblit-0d32645ba2eafb1abfdb85bbe358d4db5e929aba.tar.gz
gitblit-0d32645ba2eafb1abfdb85bbe358d4db5e929aba.zip
Typo in setup_transport_http.mkd
-rw-r--r--src/site/setup_transport_http.mkd2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/site/setup_transport_http.mkd b/src/site/setup_transport_http.mkd
index 5329a188..4de75963 100644
--- a/src/site/setup_transport_http.mkd
+++ b/src/site/setup_transport_http.mkd
@@ -5,7 +5,7 @@
You must tell Git/JGit not to verify the self-signed certificate in order to perform any remote Git operations.
**NOTE:**
-The default self-signed certificate generated by Gitlbit GO is bound to *localhost*.
+The default self-signed certificate generated by Gitblit GO is bound to *localhost*.
If you are using Eclipse/EGit/JGit clients, you will have to generate your own certificate that specifies the exact hostname used in your clone/push url.
You must do this because Eclipse/EGit/JGit (< 3.0) always verifies certificate hostnames, regardless of the *http.sslVerify=false* client-side setting.