From: "John Norris" <john@norricorp.f9.co.uk>
To: git@vger.kernel.org
Subject: Smart HTTP
Date: Mon, 13 Oct 2014 17:29:05 +0000 [thread overview]
Message-ID: <em4fcc6297-a9c0-4bcf-b7da-6afb6cbe5f80@mesh> (raw)
Hi,
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.
Regards,
John Norris
next reply other threads:[~2014-10-13 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 17:29 John Norris [this message]
2014-10-13 18:58 ` Smart HTTP Konstantin Khomoutov
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=em4fcc6297-a9c0-4bcf-b7da-6afb6cbe5f80@mesh \
--to=john@norricorp.f9.co.uk \
--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).