It seems that the HTTP response from a POST to the /write end point does not include a Content-Length: header. This is unfortunate when you’re trying to do HTTP/1.1 and want to stream the HTTP requests through a single connection. Without the content length in the response, I can’t tell when the response is complete unless the connection closes. But with HTTP/1.1 and no “Connection: close” header, we never do…
Upon closer look, it seems to be when the status is “204 No Content” and there will be no response body. I can’t really figure out from the RFC whether it would not also need a Content-Length: 0 header to emphasize that.