general/4367: Transfer-Encoding: chunked: chunk-size ends with a space

[John Stracke <fr...@thibault.org>]

>Number:         4367
>Category:       general
>Synopsis:       Transfer-Encoding: chunked: chunk-size ends with a space
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri May  7 11:30:00 PDT 1999
>Last-Modified:
>Originator:     francis+bug@thibault.org
>Organization:
apache
>Release:        1.3.3
>Environment:
Linux ariel 2.0.36 #1 Mon Jan 4 23:16:56 EST 1999 i586 unknown
gcc 2.7.2.3 (linked with g++, in order to be able to use C++ in DSO modules).
>Description:
I'm developing a module, which generates its output on the fly, so, under
HTTP/1.1, Apache sends the entity-body with Transfer-Encoding: chunked.  The
first chunk-size is sometimes followed by a space, which is a violation of the
RFC.
>How-To-Repeat:
Mmm, I'm afraid I can't give you the code to the module.  If the problems's
nonobvious, I might be able to come up with a small test case.  I'm not sure,
though, since I don't know why it doesn't always happen.  I was hoping it would
be something obvious, like somebody didn't quite read the spec right and stuck
in a padding space.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]