Re: [PATCH 2/3] http: try standard proxy env vars when http.proxy config option is not set
- From
Daniel Stenberg <daniel@haxx.se>
- Date
- Mar 4, 2012, 19:19 UTC
- Message-ID
- <alpine.DEB.2.00.1203042013410.5351@tvnag.unkk.fr>
- In-Reply-To
- <7v62eqzrqm.fsf@alter.siamese.dyndns.org>
On Tue, 28 Feb 2012, Junio C Hamano wrote:
Show 8 quoted lines
>> * Why do you (need to?) support HTTP_PROXY when curl doesn't? > > Let me add a third bullet point. > > I've heard rumors that libcurl on some versions/installations of Mac OS X > deliberately ignores the environment. For those who agree with Apple, it > would be a regression if we suddenly start the environment ourselves and > using it.
I can also add that in libcurl we completely deliberately do not support "HTTP_PROXY" (using all upper case) for a quite simple and boring reason:
The (very old) CGI interface that web servers use(d) to invoke programs server-side passes on header values in environment variables named "HTTP_[header]". So if you send a request to a server that starts a CGI script and use a request header named Proxy: in that request, that header will be passed to the CGI script using the environment variable "HTTP_PROXY" ...
-- / daniel.haxx.se