git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: jean.guyader@linkea.org, git@vger.kernel.org,
	Jean Guyader <jean.guyader@gmail.com>
Subject: Re: [PATCH] Fix problem with authentification on http repository.
Date: Tue, 08 Jul 2008 22:44:58 -0700	[thread overview]
Message-ID: <7v4p6zmx0l.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7v4phdja01.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 29 Sep 2007 17:02:38 -0700")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Sat, 29 Sep 2007, Junio C Hamano wrote:
>
>> We never supported URLs with embedded credentials (see
>> Documentation/urls.txt), partly because nobody asked for it, but
>> more importantly because giving -n to curl to have it read from
>> user's .netrc is generally much more preferred approach.
>
> To elaborate on that: if you fetch from somewhere, your url, username and 
> password can be read from the output of "ps ax | grep http" very easily.

Actually Documentation/howto/setup-git-server-over-http.txt
talks about http://user@server/path/ format.  How well does this
work in practice?  If it does, we should update Documentation/urls.txt
to allow optional user@ there like...

---

 Documentation/urls.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index e67f914..c9aab86 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -6,8 +6,8 @@ to name the remote repository:
 
 ===============================================================
 - rsync://host.xz/path/to/repo.git/
-- http://host.xz/path/to/repo.git/
-- https://host.xz/path/to/repo.git/
+- http://{startsb}user@{endsb}host.xz/path/to/repo.git/
+- https://{startsb}user@{endsb}host.xz/path/to/repo.git/
 - git://host.xz/path/to/repo.git/
 - git://host.xz/~user/path/to/repo.git/
 - ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/

  reply	other threads:[~2008-07-09  5:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29 22:26 [PATCH] Fix problem with authentification on http repository jean.guyader
2007-09-29 23:10 ` Johannes Schindelin
2007-09-29 23:38 ` Junio C Hamano
2007-09-29 23:40   ` Johannes Schindelin
2007-09-30  0:02     ` Junio C Hamano
2008-07-09  5:44       ` Junio C Hamano [this message]
2008-07-09  5:51         ` Mike Hommey
2008-07-09  6:28           ` Junio C Hamano
2008-07-09  7:53             ` Mike Hommey
2008-07-09  8:04               ` Daniel Stenberg
2008-07-09  8:18               ` Junio C Hamano
2008-07-09  8:56                 ` Mike Hommey
2008-07-09 11:43                   ` Johannes Schindelin
2008-07-10  7:24                     ` Jeff King
2008-07-10  7:32                       ` Junio C Hamano
2008-07-10  8:47                         ` Jeff King
2008-07-10 10:51                       ` Johannes Schindelin
2008-07-10 11:30                         ` Andreas Ericsson

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=7v4p6zmx0l.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jean.guyader@gmail.com \
    --cc=jean.guyader@linkea.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).