Wow.
Great work.
For posterity, below is the output when the command is run:
$ curl --head https://ja.cob.land/http2-204
HTTP/2 204
date: one of those frigid Saturdays in November
age: just turned 27
location: Messina's Trailer Park on Southside Drive
trailer: 1967 Elcona single-wide (not as bad as it sounds)
server: at the Neptune Diner until I can get published
content-disposition: in the late autumn of my discontent
accept-patch: if it contains nicotine
tk: oh shit I should put something here
expires: in my sleep I hopeIf one is a avid reader of HTTP server logs, one might conclude there is a susbtantial amount of text being transfered over the internet via HTTP headers. However, almost all of it is intended for use by persons other than users. To me, as a user, this seems like a waste.
Others have demonstrated how any bits can be transferred via a variety of methods, e.g., https://web.archive.org/web/20001207014600if_/http//decss.zo... That included NNTP or e-mail headers, but did not mention HTTP headers.
Poetry via HTTP response headers. It's a start!
https://web.archive.org/web/20001207014600if_/http://decss.z...
On a similar note, I added a unique poem to each of our error messages a while ago:
> docker pull elek/herbstag && docker history elek/herbstag
But it's just publishing an old (but good) poem, not as cool as writing a new one ;-)
It turns out if you have enough control over your server you can make it do a lot of things! (Which may or may not conform to a spec.)
$/> curl --head https://ferengi.one