git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Smart HTTP

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Oct 13, 2014, 18:58 UTC
Message-ID
<20141013225822.47d4deb70751eeb4915f69d6@domain007.com>
In-Reply-To
<em4fcc6297-a9c0-4bcf-b7da-6afb6cbe5f80@mesh>

On Mon, 13 Oct 2014 17:29:05 +0000 "John Norris" <john@norricorp.f9.co.uk> wrote:

Show 9 quoted lines
> I guess this comment is aimed at Scott Chacon.
> I have read your blog post on Smart HTTP 
> (http://git-scm.com/blog/2010/03/04/smart-http.html) and wondered if 
> there is any documentation that compares in terms of thoroughness
> with your sections in the book on using SSH, which does explain the
> basics so that "anyone" can get it working.
> I have tried setting up authenticated pull and push with HTTP (not 
> HTTPS) and Apache never asks for authentication during a pull and 
> refuses a push with a 403 error.
Looks like a sort-of followup to this discussion [1].

(John, being a good netizen, you should have included the link to that discussion yourself, to put your uh comment in context and may be actually get some useful responses.)

1. https://groups.google.com/d/topic/git-users/zcXYY1Le_F4/discussion
Previous: John Norris
Message 2 of 2 in “Smart HTTP”
  1. John NorrisOct 13, 2014
  2. Konstantin KhomoutovOct 13, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.