HTTP response without content-length doesn't work

Swamp Thing · Jan 22, 2024

I am trying out the web server feature on a NodeMCU ESP8266 board. If I include a Content-Length line in the response header, it works perfectly.

But if I omit the content-length, then Chrome and Firefox fail to display the page. Chrome displays a blank page, and Firefox says "Connection was reset".

This is the HTTP response as received on Telnet:

Code:

HTTP/1.1 200 OK
Content-Type: text/html
Connection: close

<html><body>Hello</body></html>
Connection closed by foreign host.

(There is a "\r\n" at the end of each line and after the header).

Curl and Wget also report "connection closed" errors.

My understanding is that if content-length is not specified, then closing the connection is a valid way to signal end of data. Especially with "connection: close". So what is the problem?

harborsparrow · Jan 22, 2024

The Content-Length header is mandatory for messages with entity bodies, unless the message is transported using chunked encoding. Some info on chunked encoding is here: https://en.wikipedia.org/wiki/Chunked_transfer_encoding

HTTP response without content-length doesn't work

Related to HTTP response without content-length doesn't work

Why does an HTTP response without a Content-Length header not work?

What are the alternatives to using the Content-Length header?

How can I troubleshoot an HTTP response issue related to missing Content-Length?

Is it mandatory to include the Content-Length header in all HTTP responses?

Can HTTP/2 handle responses without a Content-Length header better than HTTP/1.1?

Similar threads

Hot Threads

Recent Insights