HTTP is fundamental to modern development, from frontend to backend to mobile. But like any widespread mature standard, it’s got some funky skeletons in the closet.
Some of these skeletons are little-known but genuinely useful features, some of them are legacy oddities relied on by billions of connections daily, and some of them really shouldn’t exist at all. Let’s look behind the curtain.
Did know about that
Expect: 100-continue header — and even found a bug in curl handling an intermediary HTTP 417 response — but most of the stuff — such as the HTTP Trailers — were new to me.