4 ms·

IIRC from when I wrote a basic http server, the problem with CGI is that you have to store the output of the script in memory in order to insert the Content Len

IIRC from when I wrote a basic http server, the problem with CGI is that you have to store the output of the script in memory in order to insert the Content Length field value in the http respondse header. It seems like a rather innefficient operation, especially if repeated a million times on a server. Else you could just read from the your CGI process in a non blocking manner, writing back to the socket whenever output is available. Am I correct ?

sdflhasjd 4y ago
You can use chunked transfer encoding to send data of unknown length.
habibur 4y ago
transfer-encoding: chunked, and then send data in 64kb packets. You need to tell the size of each packet at its header. Even then, it is an optional good practice, but not required by RFC.