Re: CURLOPT_HTTP_VERSION doesn't work?
Date: Wed, 7 Jan 2009 22:09:56 -0800
On Wed, Jan 07, 2009 at 11:31:32PM -0500, A. Craig West wrote:
> I was about to say that I couldn't think of any use cases where we
> might want to specify the two versions separately, and as I was about
> to craft an amazing reply itemizing the possibilities, I realized that
> there is an obvious one: HTTP1.1 proxy, HTTP1.0 destination server.
> The opposite case doesn't make much sense, as I am pretty sure a 1.0
> compliant proxy won't forward 1.1 connections in any case, but we
> might as well allow it to try :-)
I don't see why it wouldn't. Once the connection has been made, the proxy
should stay out of the way and allow any data straight through.
> I suspect the logic will be a lot simpler with a separate option,
> CURLOPT_PROXY_HTTP_VERSION. Where else besides CONNECT do we
> communicate with the proxy as a distinct entity from the destination
> server? I suppose I will find out tomorrow...
I can't think of any besides SOCKS proxies.
-- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has movedReceived on 2009-01-08