Frankly, I can live without git traffic over HTTP at the moment, but not without the git subdomain, which is just super duper intuitive :)
I really look forward to that improvement you just mentioned! Good work! Sidhant On Jun 23, 2011, at 9:59 PM, Marius Mårnes Mathiesen wrote: > On Thu, Jun 23, 2011 at 5:21 PM, Sidhant Gupta <[email protected]> wrote: > I got it to work, though I did not change anything. I think it was also a > problem on my browser side with some stale cookies or something. > > Great! > > About using "git" as first part of the FQDN, I updated the > HTTP_CLONING_SUBDOMAIN to something other than "git" and the warning during > app start up in production.log also went away. > > I hope "git" is not hard coded anywhere else as first part of FQDN. > > The main reason we have reserved the git. subdomain is that we use this to > detect git-over-http requests. There's a tiny module called before every > request, trying to determine whether we're receiving Git traffic over HTTP - > in which case it's handled appropriately. > > We're currently working on a replacement for the entire git-http > functionality, introducing a separate app/component that will support both > push and pull over HTTP(S). This will be A Big Deal (tm) for simplifying the > installation of Gitorious, and will involve running a separate daemon to > handle this - ie. the main application won't have to deal with this anymore. > > Cheers, > - Marius > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
