Feature #27366
support clone/fetch via http://
| Status: | Resolved | Start date: | 2011-06-10 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Steffen Gebert | % Done: | 0% |
|
| Category: | Gerrit | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Due to firewall restrictions it is sometimes not possible to clone/fetch via git:// (or ssh://) protocol. That's where http:// comes in handy.
Unfortunatly the domain/url scheme that is currently setup provides gitweb access via http:// on the clone/fetch url.
IMO we need to switch gitweb to some other location (http://gitweb.typo3.org for example)
feedback anyone?
History
Updated by Karsten Dambekalns almost 2 years ago
With the "smart HTTP protocol" (the default nowadays IIRC) having both on the same URL is possible, no?
Updated by Peter Niederlag almost 2 years ago
What do you mean by "smart HTTP protocol"?
gitweb and upload/fetch-pack (as invoked from git daemon?) seems to be pretty different to me and I don't know if it works out to serve gitweb and git on same port and hostname via http://.
Updated by Karsten Dambekalns almost 2 years ago
Peter Niederlag wrote:
What do you mean by "smart HTTP protocol"?
http://progit.org/2010/03/04/smart-http.html
gitweb and upload/fetch-pack (as invoked from git daemon?) seems to be pretty different to me and I don't know if it works out to serve gitweb and git on same port and hostname via http://.
http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html explains:
To serve gitweb at the same url, use a ScriptAliasMatch to only those URLs that git http-backend can handle, and forward the rest to gitweb:
ScriptAliasMatch \
"(?x)^/git/(.*/(HEAD | \
info/refs | \
objects/(info/[^/]+ | \
[0-9a-f]{2}/[0-9a-f]{38} | \
pack/pack-[0-9a-f]{40}\.(pack|idx)) | \
git-(upload|receive)-pack))$" \
/usr/libexec/git-core/git-http-backend/$1
ScriptAlias /git/ /var/www/cgi-bin/gitweb.cgi/
That being said, for those being in such a situation they can use https://review.typo3.org/p/... just fine, even temporarily as needed. Of course for clone and simple (non-review-related) fetches it would be nice if that did not put load on the review server, but it works already.
Updated by Jo Hasenau almost 2 years ago
That being said, for those being in such a situation they can use https://review.typo3.org/p/... just fine, even temporarily as needed. Of course for clone and simple (non-review-related) fetches it would be nice if that did not put load on the review server, but it works already.
Currently we are trying to connect to https://review.typo3.org using the settings mentioned in the Tips & Tricks section of the wiki due to firewall restrictions. The https-connect seems to work but then we get a "403 - forbidden" for the URL and the clone process fails.
Testing the same URL within the adress bar of the browser gives the same 403, so it seems that https-access to the repository is broken.
Updated by Steffen Gebert 5 months ago
- Category set to Gerrit
- Status changed from New to Resolved
- Assignee set to Steffen Gebert
Possible now for both git.typo3.org (through gitweb) and also enabled in gerrit