WGLC issue: ambiguity in part 1 example

Amos Jeffries <squid3@treenet.co.nz> Sun, 17 February 2013 01:30 UTC

Resent-Date: Sun, 17 Feb 2013 01:28:29 +0000
Resent-Message-Id: <E1U6t3N-0007p4-SR@frink.w3.org>
Message-ID: <51203212.9000009@treenet.co.nz>
Date: Sun, 17 Feb 2013 14:27:46 +1300
From: Amos Jeffries <squid3@treenet.co.nz>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=58.28.153.233; envelope-from=squid3@treenet.co.nz; helo=treenet.co.nz
Subject: WGLC issue: ambiguity in part 1 example
Archived-At: <http://www.w3.org/mid/51203212.9000009@treenet.co.nz>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Part 1 section 2.1 example server response contains an entity body and a 
Content-Length header.

The Content-Length header is 2 bytes larger than the visible/printable 
bytes in the entity and it is not made clear that there are invisible 
trailer bytes being included in the in the displayed entity size.

I think at this early stage of the texts it would be best to keep things 
simple and only have the Content-Length equal to the visible bytes - 
"Hello world!" being 12 bytes long.

Amos

Re: WGLC issue: ambiguity in part 1 example Mark Nottingham
WGLC issue: ambiguity in part 1 example Amos Jeffries
#433, was: WGLC issue: ambiguity in part 1 example Julian Reschke
Re: WGLC issue: ambiguity in part 1 example Roy T. Fielding
Re: WGLC issue: ambiguity in part 1 example Amos Jeffries
Re: WGLC issue: ambiguity in part 1 example Roy T. Fielding