On Fri, Jun 27, 2008 at 12:00:35AM +0100, Phil Blundell wrote:
> I've never seen it in the wild; I noticed this while testing our
> application against a proprietary testsuite.
>
> I guess I didn't make it very clear in my original mail that the current
> behaviour of curl is to leave the connection hung if it encounters any
> code between 101 and 199 inclusive. For all codes between 102 and 199,
> there odesn't seem to be any ambiguity: either possible reading of the
> RFC would indicate that you should treat them like 100.

That's an unacceptable response by default.

> As for 101, no matter which interpretation you place on the RFC it is
> hard to see that the behaviour with this patch would be worse than that
> without. Without the patch you will just get a hung transfer. With the
> patch you will probably still get a hung transfer though perhaps for
> different reasons. Practically speaking, though, you should never see a
> 101 response if you didn't send an Upgrade header, so it seems pretty
> unlikely that this will be a problem in practice.

Once the problem of an automatic hung transfer is fixed, then the choice
has to be made whether to ignore the 1xx code or cleanly err out the
transfer.

>>> Dan

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