git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>,
	git@vger.kernel.org, sam@vilain.net, spearce@spearce.org
Subject: Re: [PATCH v5 2/5] http: handle proxy proactive authentication
Date: Thu, 12 Apr 2012 18:42:30 -0400	[thread overview]
Message-ID: <20120412224230.GA22988@sigill.intra.peff.net> (raw)
In-Reply-To: <7vd37c4msm.fsf@alter.siamese.dyndns.org>

On Thu, Apr 12, 2012 at 03:18:01PM -0700, Junio C Hamano wrote:

> > So as far as I can tell, these are equivalent:
> >
> >   http_proxy=http://127.0.0.1:1080
> >   http_proxy=https://127.0.0.1:1080
> >   http_proxy=foobar://127.0.0.1:1080
> 
> Yes, that is exactly what I was trying to say.  The foobar:// part does
> not matter; "http" in "http_proxy" is what matters, as it is how you can
> specify two separate proxies depending on what destination you are going
> via what protocol.

But you snipped the later part of my message, which is that the "http"
in "http_proxy" does _not_ matter. It is about which destinations to
apply the proxy to, not how you talk to the proxy (and the latter is what
should matter for the credentials).

> > Not splitting "http" and "http-proxy" does have a slight confusion, as
> > the default proxy port is "1080". So a proxy of "http://127.0.0.1" would
> > mean "http://127.0.0.1:1080", whereas a regular request would mean
> > "http://127.0.0.1:80". The credential code includes the port as part of
> > the unique hostname, but since the default-port magic happens inside
> > curl, we have no access to it (short of re-implementing it ourselves).
> 
> Ok, so how about this as a replacement patch for what I have had for the
> past few days?

My other message argued "the http-proxy distinction might be important,
but probably isn't". But I didn't talk about "the http-proxy distinction
might break helpers". The stock helpers will be fine; they are totally
clueless about what the protocol means, and just treat it as a string to
be matched. But for something like osxkeychain, where it is converting
the protocol string into some OS-specific magic value, it does matter,
and http-proxy would cause it to exit in confusion.

It looks like OS X defines a SOCKS type and an HTTPProxy type for its
keychain API. So in either case, it should probably be updated to handle
these new types. And I guess that argues for making the distinction,
since at least one helper does want to care about it.

-Peff

  reply	other threads:[~2012-04-12 22:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 14:03 [PATCH v5 2/5] http: handle proxy proactive authentication Nelson Benitez Leon
2012-04-09 21:39 ` Junio C Hamano
2012-04-10  0:59   ` Junio C Hamano
2012-04-12 15:54     ` Junio C Hamano
2012-04-12 20:58       ` Jeff King
2012-04-12 21:25         ` Junio C Hamano
2012-04-12 22:05           ` Jeff King
2012-04-12 22:18             ` Junio C Hamano
2012-04-12 22:42               ` Jeff King [this message]
2012-04-13 19:35                 ` Junio C Hamano
2012-04-13 20:23                   ` Jeff King
2012-04-13 20:56 ` Jeff King
2012-04-19 17:09   ` Junio C Hamano

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=20120412224230.GA22988@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nelsonjesus.benitez@seap.minhap.es \
    --cc=sam@vilain.net \
    --cc=spearce@spearce.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).