« Atomified vs. Atomized | Main | Atom Landscape Overview »

Friday, November 09, 2007


Feed You can follow this conversation by subscribing to the comment feed for this post.

Adrien de Croy


Just saw your comments on my I-D. The spec for HTTP (RFC2616) mentions interim responses, with status codes in the range 100 - 199.

It states that HTTP agents must be prepared to receive any number of interim responses prior to the final response (2xx - 5xx).

I've never actually seen more than 1 interim response (e.g. IIS responds with "100 continue" to a POST request, followed by another response message with the actual result of the POST). But this already is 1:2 for POST, which indicates User agents have already been coded to deal with interim responses.

The requirement for agents to handle any number of interim responses means this proposal doesn't contravene the spec in terms of message flow.


thanks a lot for your comment, adrian!

http://tools.ietf.org/html/rfc2616#section-10.1 indeed states that "a client MUST be prepared to accept one or more 1xx status responses prior to a regular response". so http definitely allows 1:n message patterns, and not only 1:1.

http://tools.ietf.org/html/rfc2616#section-6 however says (like i wrote in my original post) that "after receiving and interpreting a request message, a server responds with an HTTP response message".

these two statements are not completely contradicting, but at least not as clear as one might wish. i found the quote in section 6 and (wrongfully) concluded that there would be just one response. maybe this part of the spec also would be a candidate for the ongoing effort to create a clarified version of the http spec (http://www.ietf.org/html.charters/httpbis-charter.html)?

The comments to this entry are closed.