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

RE: Padding size in chunked encoding

From: John Franks <john@math.nwu.edu>
Date: Fri, 21 Feb 1997 12:36:26 -0600 (CST)
To: "Phillip M. Hallam-Baker" <hallam@ai.mit.edu>
Cc: HTTP Working Group <http-wg@cuckoo.hpl.hp.com>
Message-Id: <Pine.SUN.3.95.970221123519.25198B-100000@hopf.math.nwu.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2521
On Fri, 21 Feb 1997, Phillip M. Hallam-Baker wrote:

> This problem could be cleanly solved if we could zero pad the size
> of a chunk.  I.e. if a chunk size could look like
> 
>                  0057CRLF
> 
> The current BNF disallows this, however.  Is there some reason for
> disallowing a leading zero?  If this cannot be changed I suspect
> we will end up with rather inelegant extensions like
> 
>                  57;pad="xxx"CRLF
> 
> with a variable number of x's adjusted to create the padding.
> 
> 
> John is right, but this was discussed at length at the time. I've
> never heard a reasoned argument aginst the leading zeros but
>  it didn't get fixed then and its too late now.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Is it?  I thought changes in the light of implementation experience
were sometimes possible.

John Franks 	Dept of Math. Northwestern University
		john@math.nwu.edu
Received on Friday, 21 February 1997 10:37:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:01 UTC