You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Dean Gaudet <dg...@arctic.org> on 2000/03/02 08:42:54 UTC

RE: [Not yet a PATCH] Extra CRLF in chunked response (fwd)

[hrm, brian did you remove my other posting addresses?  testing with the
address i actually receive this list with...]

---------- Forwarded message ----------
Date: Wed, 1 Mar 2000 23:27:00 -0800 (PST)
From: Dean Gaudet <dg...@arctic.org>
To: new-httpd@apache.org
Subject: RE: [Not yet a PATCH] Extra CRLF in chunked response
X-comment: visit http://arctic.org/~dean/legal for information regarding
    copyright and disclaimer.



On Thu, 2 Mar 2000, William A. Rowe, Jr. wrote:

> Here is what is SO ODD... the 57 in the 3rd block is followed by 2 spaces

that is by design (and is permitted by rfc2068/2616).  rfc2068 didn't
permit us to use leading 0s... although rfc2616 does permit leading 0s i'd
rather not change the behaviour now.

> and then a single CRLF, it is NOT followed by a blank line before the block
> data!!!

there shouldn't be an *extra* blank line at all.  i'm guessing the blank
lines you're seeing are not part of your data?

i think i see what the problem is, and about a dozen other problems.

now i'll just have to go guess what the latest configuration instructions
are so that i can compile the code (it doesn't look like anyone updated
any of the top-level READMEs...)

Dean