git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bo98 <BoEllisAnderson@aol.com>
To: git@vger.kernel.org
Subject: Re: PROPFIND 405 with git-http-backend and Smart HTTP
Date: Mon, 30 Jul 2012 01:40:00 -0700 (PDT)	[thread overview]
Message-ID: <1343637600904-7564056.post@n2.nabble.com> (raw)
In-Reply-To: <CAJo=hJtB6OQ8+8Q_JgPoAntOdQ=Z0tOERYRD7wJ0LRLgacYA8A@mail.gmail.com>


Shawn Pearce wrote
> 
>> And here's a snip from my access_log:
>>
>>     ::1 - - [29/Jul/2012:18:34:34 +0100] "GET
>> /repo/myproject.git/info/refs?service=git-receive-pack HTTP/1.1" 200 117
> 
> Was this request actually served using the smart http-backend? Try the
> request yourself on the command line with curl, making sure to pass
> the ?service=git-receive-pack query parameter. A smart HTTP response
> will include a service=git-receive-pack line as the first line of the
> response body. I don't think Apache called the http-backend CGI, and
> so the client thought the server was not smart HTTP capable.
> 

This is what curl returned:

2ddf56592a0f55456b8c42dc9f2cb9289f083f53	refs/heads/1.0.x
55079bb13d9af8a9164ad0d24b654cbfe119bc7e	refs/heads/master

Looks okay. Those are the 2 branches I've got.



--
View this message in context: http://git.661346.n2.nabble.com/PROPFIND-405-with-git-http-backend-and-Smart-HTTP-tp7564017p7564056.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2012-07-30  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-29 18:52 PROPFIND 405 with git-http-backend and Smart HTTP Bo98
2012-07-30  1:00 ` Shawn Pearce
2012-07-30  8:40   ` Bo98 [this message]
2012-07-30 16:37     ` Shawn Pearce
2012-07-30 20:30       ` Bo98
2012-07-30 20:42         ` Shawn Pearce
2012-07-30 21:39           ` Bo98
2012-08-05 18:30             ` Drew Northup
2014-08-14 10:23               ` lpicquet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1343637600904-7564056.post@n2.nabble.com \
    --to=boellisanderson@aol.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).