You just did raise this as a potential bug, but you need to convince me that Bitcoin is not following the HTTP/1.1 spec, which says:
... and, for 'tolerant' applications:
What character(s) is JayRock putting between the headers and the body?