Jeff King <peff@xxxxxxxx> writes: > Something like the (largely untested) patch below. That would also make > it easy to support arbitrary amounts of whitespace after the header, > which I think are allowed by the standard (whereas now we'd parse > "Content-type: text/plain" as " text/plain", which is silly). > > Worth doing? The result does look cleaner. I do not think we've seen much polishing in this area of the code for quite a long time, which might indicate that what we have may be good enough, but at the same time it would mean it is quiescent time for the code and it is safe to clean it up.
