Hi Marius,

I've already installed and enabled the mod_xsendfile on Apache (Ubuntu 
Server 12.04) and my gitorious-ssl file is this:

<IfModule mod_ssl.c>
    <VirtualHost *:443>
        ServerName gitorious.eng.it
        DocumentRoot /var/www/gitorious/public
        SSLEngine on
        XSendFile on
        XSendFilePath /var/www/gitorious/tarballs
        SSLCertificateFile    /etc/ssl/certs/ssl-gitorious.crt
        SSLCertificateKeyFile /etc/ssl/certs/ssl-gitorious.key
        BrowserMatch ".*MSIE.*" nokeepalive ssl-unclean-shutdown 
downgrade-1.0 force-response-1.0
    </VirtualHost>
</IfModule>

Obviously on my local machine hosts file I have the mapping of 
IP_GITORIOUS gitorious.eng.it git.gitorious.eng.it

Regards

Il giorno martedì 18 dicembre 2012 08:54:05 UTC+1, Marius Mårnes Mathiesen 
ha scritto:
>
>
> Graziano Aliberti writes: 
>
> > Hi everyone, 
> > 
> > I've installed a local gitorious instance without problems except that I 
> > can't clone over https and over git. 
> > 
> > When I write : 
> > 
> > git clone git://gitorious.eng.it/example/example.git example 
> > 
> > I receive 
> > 
> > Cloning into 'example'... 
> > fatal: protocol error: expected sha/ref, got ' 
> > ---------------------------------------------- 
> > Unable to access repository /example/example.git 
> > ----------------------------------------------' 
>
> Graziano, 
> Looks like you need to set up either mod_xsendfile (Apache) or 
> X-Accel-Redirect (Nginx) to have your frontend web server deliver the 
> Git objects over HTTP for you. 
>
> There's some information about this on the wiki (this assumes you're 
> using Apache): 
>
>   
> https://gitorious.org/gitorious/pages/GitoriousComponents#HTTP+cloning++[2] 
>
> If you're using Nxinx, this paragraph on the getgitorious.com site: 
> http://getgitorious.com/documentation/gitorious-org-setup.html#sec-1-2-2[3] 
> explains how to set that up. 
>
> Cheers, 
> - Marius 
>

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to