Consistently capitalized all instances of Content-* headers

[vedranmiletic]

Replaced Content-type and Content-length with Content-Type and Content-Length for consistency with the rest of the codebase. Additionally, while HTTP/1.1 headers are case-insensitive according to the RFC 2616, the capitalization used in the document is Content-Type and Content-Length.

Tested locally on the default build configuration and no breakages have been observed.

[nikic]

This seems like a harmless change, but also not a particularly useful one. @cmb69 Do you see any issues with doing this?

[vedranmiletic]

@nikic thanks, I know it's not anything major. I'm using PHP for teaching how HTTP works and it would be nice to have the headers appear in a consistent manner.

[kamil-tekiela]

I was thinking of proposing the same, but I decided it wasn't worth my time. I see nothing wrong with changing the capitalization.

[cmb69]

I'm very much with @nikic here. The potential BC break for code and tests assuming case-insensitive headers is slightly concerning; OTOH, this might a chance for such code to be fixed. Maybe write to the internals list?

[krakjoe]

There is potential for breakage and very low value in the change itself.

Because of that, I'm closing this one.

If you want to start a conversation about it on internals, this may be re-opened if the consensus gathered there is different to the apparent consensus here.

Thanks for putting in the effort.