* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #300 (closed design: fixed)

Opened 3 years ago

Last modified 3 years ago

Define non-final responses

Reported by: mnot@pobox.com Owned by: draft-ietf-httpbis-p1-messaging@tools.ietf.org
Priority: normal Milestone: 18
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin:

Description

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.

Attachments

300.diff (947 bytes) - added by julian.reschke@gmx.de 3 years ago.
Proposed patch

Change History

comment:1 Changed 3 years ago by mnot@pobox.com

Suggest putting it in the new section on message orientation.

comment:2 Changed 3 years ago by mnot@pobox.com

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

comment:3 Changed 3 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 16

comment:4 Changed 3 years ago by julian.reschke@gmx.de

  • Milestone changed from 16 to 17

comment:5 Changed 3 years ago by julian.reschke@gmx.de

  • Milestone changed from 17 to unassigned

comment:6 Changed 3 years ago by mnot@pobox.com

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).

Changed 3 years ago by julian.reschke@gmx.de

Proposed patch

comment:7 Changed 3 years ago by julian.reschke@gmx.de

From [1471]:

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

comment:8 Changed 3 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 18

comment:9 Changed 3 years ago by julian.reschke@gmx.de

See also [1537]

comment:10 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:11 Changed 3 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.