HTTP header and Content-Type

AFAICT, the last line of an HTTP header is always Content-Type, which means the content begins after the next newline.

However, I was just googling around and I cannot find it stated anywhere by anyone that this *must* be the case, ie, a server could return Content-Type as the first line of the header. That means the above method is not guaranteed to succeed. Does anyone know how you are supposed to determine where a header ends and the content begins?

What language are you processing with? I assume you've returned a large blob and now you're trying to parse it. Is this a last-chance move to try and extract the content?

There's nothing in the HTTP spec that states that the Content-Type header must come last in the stream before the content.

I'm working in C. I've never had a problem just using the Content-Type as the boundary, but now I am required to provide a reliable product for someone else I wanted to make sure this practice (don't remember where I picked it up!) is well, reliable.

Anyway, I think the problem is solved as I found this in RFC 2616, sec 4:

Both types of message consist of a start-line, zero or more header fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header fields, and possibly a message-body.

Whew! Glad I checked...