HTTP 2.0 Will Be a Binary Protocol
earlzdotnet writes "A working copy of the HTTP 2.0 spec has been released. Unlike previous versions of the HTTP protocol, this version will be a binary format, for better or worse. However, this protocol is also completely optional: 'This document is an alternative to, but does not obsolete the HTTP/1.1 message format or protocol. HTTP's existing semantics remain unchanged.'"
That's my point -- you can't simply skip to the next line. Where a HTTP header's value ends and the next header begins is dependent on the header. They can even span multiple lines. Custom headers are impossible to parse correctly, so implementations usually just assume they'll be on a single line, or maybe quoted like some of the standard headers allow.