Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#57 closed editorial (fixed)

Status Code and Reason Phrase

Reported by: mnot@… Owned by:
Priority: Milestone: 02
Component: p1-messaging Severity:
Keywords: Cc:

Description

6.1.1 is apparently a bit too vague about how applications should parse and process the information, making some implementations parse the reason phrase (probably exact matches on the complete status line, not just status code) to determine the outcome.

There should be a SHOULD requirement or equivalent that applications use the status code to determine the status of the response and only process the Reason Phrase as a comment intended for humans.

It's true that later in the same section there is a reverse MAY requirement implying this by saying that the phrases in the rfc is just an example and may be replaced without affecting the protocol, but apparently it's not sufficient for implementers to understand that applications should not decide the outcome based on the reason phrase.

Change History (6)

comment:1 Changed 11 years ago by mnot@…

I propose rewording the last sentence of the first paragraph "The client is not required to examine or display the Reason-Phrase." into something like

The client MAY present the Reason Phrase to the user and SHOULD NOT examine the Reason Phrase for other purposes.

or perhaps

The client SHOULD NOT examine the Reason Phrase for other purposes than displaying it to the user.

comment:2 Changed 11 years ago by mnot@…

  • Component set to messaging
  • Milestone set to unassigned

comment:3 Changed 11 years ago by fielding@…

  • Milestone changed from unassigned to 02

I suggest

The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code out of deference to earlier Internet application protocols that were more frequently used with interactive text clients. The client SHOULD ignore the content of the Reason Phrase.

....Roy

comment:4 Changed 10 years ago by fielding@…

From [198]:

Clarify that a client SHOULD ignore the Reason Phrase; related to #57.

comment:5 Changed 10 years ago by fielding@…

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [198]

comment:6 Changed 10 years ago by julian.reschke@…

From [199]:

Record "Reason Phrase" clarification in Changes seection, related to #57.

Note: See TracTickets for help on using tickets.