substack/node-parsley — pull request #1 by sethml (2011-11-11 22:37:46+00:00)
Title: Fix pipelined requests with content-length header.

When a request includes a Content-length header, it does not include a
terminating CRLF after the content - the next request begins immediately.
This change prevents us from misparsing the next request.

My brain's parser is not RFC-compliant enough to manage to extract this information from the RFC, but a quick test with each of Chrome 15, FireFox 8, and Safari 5 show this behavior, so I'm reasonably confident that it's correct.