Bug reading HTTP Reponse Status

When a server returns a HTTP response along the lines of:

HTTP/1.1 503 Service Unavailable
Content-Length: 123
Content-Type: text; charset=UTF-8
Connection: close

Some error message, maybe HTML, you get the idea.

If the server uses \n and not \r\n for newlines, the error message becomes “Service Unavailabl”.
(last character of the status code disappears)
(the same probably happens when there isn’t an error, but we can’t see it)

The same might be happening to the headers, but again: can’t see.
(but it could matter for certain stuff I would assume, but eh)

Not that it really matters too much.
Most servers do (and should) use \r\n, but it’s advised for applications to also work with \n.

(Found this while having a \n server myself)