Julia Evanswould folks be interested in an "implement a toy version of HTTP/1.1 in a weekend” guide? I'm imagining something super basic (~100 lines of Python, not remotely standards compliant), just a server that opens a TCP socket, takes HTTP requests, and returns responses.
Michael Sokolov@b0rk so no chunked encoding, ranges, gzip, keep alive, multipart mime, or other bells? Maybe target 1.0? What about POST?
@msokolov Definitely POST. I was thinking of adding a bunch of extras as exercises so that people can implement whatever bits they're interested in
Rev. GothAlice@msokolov @b0rk Gzip is a higher-level concern (transfer encoding is pretty high-level), as is MIME anything. Keep-alive is easy enough even with HTTP 1.0 v. 1.1 differences. (1.1 just makes it the default.) Chunked encoding is the low level side of this, especially as everyone forgets HTTP header "trailers". (Sending headers at the end of a chunked transfer, not the start. Useful for generating Content-MD5 and such on the fly.) POST is just a verb.
I've linked my hybrid HTTP service before. 😜