W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2007

Re: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes

From: William A. Rowe, Jr. <wrowe@rowe-clan.net>
Date: Tue, 02 Jan 2007 13:43:16 -0600
Message-ID: <459AB5D4.3030603@rowe-clan.net>
To: "Travis Snoozy (Volt)" <a-travis@microsoft.com>
CC: Mark Nottingham <mnot@mnot.net>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

Travis Snoozy (Volt) wrote:
> Mark Nottingham said:
>> Added as i54;
>>    http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/index.html#i54
>>
> <snip>
> 
> The modified proposal (after discussion) is as follows (should fix all three problems mentioned):
> 
> "A cache MUST NOT generate 1xx warn-codes for any messages except cache
> entries, and MUST NOT generate 1xx warn-codes for a cache entry except in
> response to a validation attempt for that entry. 1xx warn-codes MUST NOT be
> generated in Request messages."

Explain again how any code is passed as a Request message?  The original
language, "MUST NOT be generated by Clients" was correct.
Received on Tuesday, 2 January 2007 19:43:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:00 GMT