HTTP POST: content-length header required?

Question

I'm currently trying to optimize http-based data transfer between several applications. Our current approach, downloading first and then creating the post-request, obviously add extra IO/memory load and latencies, which I'd like to circumvent.

The core question of all:

Is it required to send a "Content-Length" header in HTTP POST requests? IIRC, HTTP 2616 declares that it's optional, but I'm not sure how applications actually behave at this point.

Talkative

For responders, see https://mcmap.net/q/47063/-is-the-content-length-header-required-for-a-http-1-0-response/632951 – Variolite

Answer 1

Depends what you mean by optional. If you mean that you can just omit the header anytime you like then no, it is not optional. The HTTP spec has very specific rules when to use that header. There are different ways of sending the data if you don't know the length. Chunked encoding for example.

4.4 Message Length

Request

In brief, for POST requests one of content-length or transfer-encoding:chunked headers should be present. – Meilhac

The documentation for "Content-Length" is now here: rfc-editor.org/rfc/rfc9110.html#name-content-length – Glia