Written by StunnByMe in


HTTP Error 418: I'm a Teapot

Okay, tired of the lame Error 404: File Not Found or the selfish Error 403: Forbidden?


Well, not anymore till I present to you ERROR 418: I'm a teapot.


It started in 1998. I don't have a computer and an internet access then. So, I didn't and you also probably didn't see that error code on your browsers ( assuming you're the same age as mine ).




Hyper Text Coffee Pot Control Protocol (HTCPCP) described in the RFC 2324 of 1998 memorandum. A 5-page memorandum that talks completely about the HTCPCP and the Error Code 418: I'm a teapot. 


Link: http://www.faqs.org/rfcs/rfc2324.html


In the RFC memo, the boys just had an introduction:



"There is coffee all over the world. Increasingly, in a world in which
   computing is ubiquitous, the computists want to make coffee. Coffee
   brewing is an art, but the distributed intelligence of the web-
   connected world transcends art.  Thus, there is a strong, dark, rich
   requirement for a protocol designed espressoly for the brewing of
   coffee. Coffee is brewed using coffee pots.  Networked coffee pots
   require a control protocol if they are to be controlled."


At that decade, experiments have started on how they can control an object ( appliance ) thru internet. Status monitors have placed on Coke Vending Machines to monitor their status.


However, the first to be on the internet is the Internet Toaster. 



An example of a HTCPCP code: ( if you want some additions asked by your barista at Starbucks )



Accept-Additions = "Accept-Additions" ":"
                          #( addition-range [ accept-params ] )

        addition-type   = ( "*"
                          | milk-type
                          | syrup-type
                          | sweetener-type
                          | spice-type
                          | alcohol-type
                          ) *( ";" parameter )
        milk-type       = ( "Cream" | "Half-and-half" | "Whole-milk"
                          | "Part-Skim" | "Skim" | "Non-Dairy" )
        syrup-type      = ( "Vanilla" | "Almond" | "Raspberry"
                          | "Chocolate" )
        alcohol-type    = ( "Whisky" | "Rum" | "Kahlua" | "Aquavit" )


There are also methods introduced for the HTCPCP:


GET method: 


        in HTTP version: means to retrieve whatever information
        in HTCPCP: The data is associated with coffee pots


WHEN method: Okay, you finish mixing the coffee. But, it's not good. Milk is introduced at this point. Use this method to say WHEN do they stop pouing milk in your coffee.




The HTCPCP has 2 return codes:


HTTP code 406: Not acceptable


        > Automated Coffee pots cannot provide additions


and HTTP/HTCPCP code 418: I'm a teapot


        > Anyone who attempts to brew a coffee on a teapot must be charged with code 418. The teapot is short, stout and made of ceramic man! You cannot brew coffee in there!






The Emacs have the plan to fully implement it, but Mozila's lack of support in the protocol
caused it to have uncontrollable bugs within the protocol.


We could have enjoy this protocol if Mozila supported it.


Some boys are reviving it. Ten years after the publication of 
RFC 2324. A fictional Web-Controlled Coffee Consortium (WC3) published a first draft of " "HTCPCP vocabulary in RDF"




Now you can drink coffee online.




YOU WANT TO SEE THE ERROR CODE?: Click ME!




resources: http://tools.ietf.org/html/rfc2324
                  http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
                   http://en.wikipedia.org/wiki/Hyper_Text_Coffee_Pot_Control_Protocol

Leave a Reply