On Thu, Jun 26, 2008 at 02:09:00PM +0100, Phil Blundell wrote:
> At the moment curl seems to react badly to an unrecognised 1xx http
> result code. Here's a patch to make any 1xx code behave the same as
> "100 continue", which seems to be the expected behaviour per the http
> RFC.

Does this occur in the wild? With which server and which conditions?
This patch sound a bit dangerous. For example, the 101 response requires
that the client switch to a different protocol, which if not done would
result in a hung transfer or otherwise unsavoury results. The RFC reads
a bit ambiguous to me. It talks about unexpected 1xx codes, but it doesn't
differentiate between an unexpected 1xx code that has been defined in
the RFC (or which there are two) or a 1xx code that has not been defined.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved