Define non-final responses

[mnot@…]

1xx responses are non-final; i.e., the underlying model is that for each request, there are 0 to many non-final responses, and exactly one final response.

This should be made explicit at a high level; it's implied by the definition of 1xx, but never really spelled out anywhere.

[mnot@…]

Suggest putting it in the new section on message orientation.

[mnot@…]

Probably also needs to be reflected in p1 2.1. Client/Server? Messaging

[mnot@…]

Proposal - add the second paragraph below to 2.1. Client/Server? Messaging:

A server responds to the client's request by sending an HTTP response message, beginning with a status line that includes the protocol version, a success or error code, and textual reason phrase (Section 3.1.2), followed by MIME-like header fields containing server information, resource metadata, and payload metadata (Section 3.2), an empty line to indicate the end of the header section, and finally a message body containing the payload body (if any, Section 3.3).

Note that 1xx responses are not final; therefore, a server can send zero to many 1xx responses, followed by exactly one final response (with any other status code).

[julian.reschke@…]

Proposed patch

[julian.reschke@…]

From [1471]:

Add a note about non-final responses to Client/Server? Messaging introduction (see #300)

[julian.reschke@…]

See also [1537]