Re: New issue: 6.1.1 too vague about parsing requirements

On Jan 11, 2007, at 1:43 AM, Henrik Nordstrom wrote:

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

Displaying to the user is problematic if you mean the browser end- 
user, because the reason phrase isn't internationalized over the  
wire, nor is it well-suited to be used as a localization lookup.

We can also derive a more enforceable style of requirement by looking  
at who's putting the reason phrase on the wire.

Perhaps something along these lines:  "Servers MUST NOT use the  
Reason Phrase for information needed by end users, because the text  
is not translatable.  Servers MUST NOT use the Reason Phrase for any  
information needed by automated agents, that is, any case that would  
require a client to try to parse or match the reason phrase in order  
to decide what to do.   Reason phrases are for debugging and logging,  
whereas it's the role of status codes to be used both to look up  
localized error messages for display to the user, and for helping  
automated agents decide whether something succeeded or failed or what  
to do next."


Received on Thursday, 11 January 2007 19:17:57 UTC