Re: https_proxy and libcurl

From: Daniel Stenberg <daniel@haxx.se>
Date: Feb 22, 2013, 22:09 UTC
Message-ID: <alpine.DEB.2.00.1302222306130.27393@tvnag.unkk.fr>
In-Reply-To: <7v7gm0c8ub.fsf@alter.siamese.dyndns.org>

On Fri, 22 Feb 2013, Junio C Hamano wrote:

Show 11 quoted lines

>>     http_proxy=http://proxy.myco.com
>>     https_proxy=https://proxy.myco.com
>>
>> The problem is that libcurl ignores the protocol part of the proxy
>> url, and it defaults to port 1080. wget honors the protocol specifier,
>> but it defaults to port 80 if none is given.
>
> IIRC, the historical norm is to set these to <host>:<port>.
>
> So many people mistakenly write them with <method>:// that some tools over 
> time learned to strip and ignore that prefix, though.

You're right, but also what exactly is the https:// _to_ the proxy supposed to mean? The standard procedure to connect to a proxy when communicating with either HTTP or HTTPS is using plain HTTP.

If you would want port 443 for a HTTPS connection to a proxy, you'd use:

   https_proxy=http://proxy.myco.com:443

Or without the ignore protocol prefix:

   https_proxy=proxy.myco.com:443

-- 
  / daniel.haxx.se