Git over HTTPS Oddity with HEAD

Sven· Jun 13, 2008, 22:59 UTC · lore

Hi

I'm using Git over HTTPS with up-to-date versions on both ends. With a populated repo, I try the following:

# git ls-remote https://git.domain.com/myapp.git HEAD

This gives me no reply at all, and indeed ...

# git ls-remote https://git.domain.com/myapp.git bb629d461b11d3c8edbc1e4f3c44085198fdaede refs/heads/master

Besides this, however, Git over HTTPS seems to work just fine and if I look inside the myapp.git on the server, a HEAD file is there:

# cat myapp.git/HEAD ref: refs/heads/master

I assume it's something fishy on the server side although I haven't done anything exotic there. Any idea what could be the reason for this?

Thanks!   -sven

PS: The background story: Capistrano (Ruby on Rails) issues the above ls-remote HEAD command during deployment, therefore not getting the head version in reply causes Capistrano to bark.