Show HN: A poem inside HTTP response headers
ja.cob.land
Show HN: A poem inside HTTP response headers
1–10 of 23 posts
Re: Show HN: A poem inside HTTP response headers
#2Happy National Poetry Month (USA), HN!
Re: Show HN: A poem inside HTTP response headers
#3When I come to HN, this is what I'm always hoping to see. Lots are here for startup news, FAANG, etc. Nope, I just want to see really, really cool fun things.
Great work.
Re: Show HN: A poem inside HTTP response headers
#4This is awesome!
On a similar note, I added a unique poem to each of our error messages a while ago:
Re: Show HN: A poem inside HTTP response headers
#5When I come to HN, this is what I'm always hoping to see. Lots are here for startup news, FAANG, etc. Nope, I just want to see really, really cool fun things. Great work.
You should probably spend more time on the Show HN section then:
Re: Show HN: A poem inside HTTP response headers
#6I was about to complain the misuse of headers and the bad choice of not using an X-* header... then I discovered RFC 6648 [0].
Wow.
Re: Show HN: A poem inside HTTP response headers
#7Very nice! By the way, I love that you explain everything, including how console commands can be run! :D
Re: Show HN: A poem inside HTTP response headers
#8This is really cool!
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 hopeRe: Show HN: A poem inside HTTP response headers
#9One project I have had in mind for many years is a direct two-way, user-to-user communication protocol or user convention that only uses HTTP request headers. One benefit would be easier-to-write clients and logging servers. There would be no need for the complexity of, and hence third party control over, a "web browser", nor the need to learn skills (HTML, CSS, Javascript, etc.) to develop and maintain a website. Users could communicate and transfer small data directly via sending and logging HTTP requests.
If 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!
Re: Show HN: A poem inside HTTP response headers
#10This is prose!