{"thread":{"id":"13937","subject":"Git over HTTPS Oddity with HEAD","startedAt":"2008-06-13T22:59:04Z","lastAt":"2008-06-13T22:59:04Z","messageCount":1,"participants":["Sven"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"79791","messageId":"loom.20080613T225103-368@post.gmane.org","threadId":"13937","inReplyTo":null,"subject":"Git over HTTPS Oddity with HEAD","fromName":"Sven","fromEmail":"svoop@delirium.ch","sentAt":"2008-06-13T22:59:04Z","receivedAt":"2008-06-13T22:59:04Z","isPatch":false,"sender":{"key":"svoop@delirium.ch","avatar":"https://gravatar.com/avatar/8fd0aed1f0e820bea8ecd9679d381055a3fc7fb404f6f0c3a5d4513cd4eb6cf7?d=mp&s=160"},"body":"Hi\n\nI'm using Git over HTTPS with up-to-date versions on both ends. With a populated\nrepo, I try the following:\n\n# git ls-remote https://git.domain.com/myapp.git HEAD\n\nThis gives me no reply at all, and indeed ...\n\n# git ls-remote https://git.domain.com/myapp.git\nbb629d461b11d3c8edbc1e4f3c44085198fdaede\trefs/heads/master\n\nBesides this, however, Git over HTTPS seems to work just fine and if I look\ninside the myapp.git on the server, a HEAD file is there:\n\n# cat myapp.git/HEAD\nref: refs/heads/master\n\nI assume it's something fishy on the server side although I haven't done\nanything exotic there. Any idea what could be the reason for this?\n\nThanks!   -sven\n\n\nPS:\nThe background story: Capistrano (Ruby on Rails) issues the above ls-remote HEAD\ncommand during deployment, therefore not getting the head version in reply\ncauses Capistrano to bark.\n"}]}