Let’s get the AMAs kicked off on Lemmy, shall we.

Almost ten years ago now, I wrote RFC 7168, “Hypertext Coffeepot Control Protocol for Tea Efflux Appliances” which extends HTCPCP to handle tea brewing. Both Coffeepot Control Protocol and the tea-brewing extension are joke Internet Standards, and were released on Apr 1st (1998 and 2014). You may be familiar with HTTP error 418, “I’m a teapot”; this comes from the 1998 standard.

I’m giving a talk on the history of HTTP and HTCPCP at the WeAreDevelopers World Congress in Berlin later this month, and I need an FAQ section; AMA about the Internet and HTTP. Let’s try this out!

  • christophski
    link
    fedilink
    English
    arrow-up
    18
    ·
    1 year ago

    What code should be used if we are expecting something to be a teapot? In this scenario it seems a 4XX is inappropriate because there is no error

    • Two9A@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      37
      ·
      1 year ago

      If you’re writing a TEA-compliant client, you’d send the BREW request and expect a 300 Multiple Options back, whereby the server will tell you which teabags are installed. You’re correct that there’ll be no error, unless all the bag stocks are out server-side.

      That’d return 503 Service Unavailable, of course.