On Wed, 27 Jun 2012, Fabian Keil wrote:

> I like the behaviour tested in 287 useful and would miss not being able to
> send custom HTTP headers in CONNECT requests with curl.
>
> I wouldn't mind if I had to use a separate option for this, though. In fact
> I would consider this an improvement, as it would allow something like:
>
> curl --header "Bla: fasel" --connect-header "Foo: bar"
> https://www.example.org/
>
> (Letting the proxy only see the header Foo, while www.example.org only sees
> the header Bla.)

Yes, I completely agree. IMO, that's how we should've done it from the
beginning when we allowed custom headers in the CONNECT. I think I'll just
proceed and add exactly that.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html