Support HTTP status 102 Processing

There’s a HTTP interim status code 102 Processing. It’s defined in RFC 2518 and can be found in the HTTP Status Code Registry.

Funnily, it has been dropped in the revised WebDAV RFC 4918, so I don’t know whether it’s worth dealing with it (RFC 4918 is from 2007 and 2518 from 1999!). However, it’s still in the status code registry, and I have just encountered a quite large WebDAV service which uses this status code (original case).

It could be exactly treated as status code 100, so I guess adding it in Http1xStream would be enough?

// HTTP_PROCESSING: 102

 if (statusLine.code != HTTP_CONTINUE || statusLine.code != HTTP_PROCESSING)
// instead of
 if (statusLine.code != HTTP_CONTINUE)

What do you think about that?

[reschke]

@yschimke - sorry for not checking before and submitting a dupe.

That said, this really needs to be treated as “bug”, not an “enhancement”.

[rfc2822]

Cool. 😎 RFC 2616 even says:

A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent.

So maybe not only 102 should be added, but all 10x status codes. But as RFC 2616 is only a rough recommendation, I don’t know whether this would be wise.