HTCPCP extension: HTCPCP-TEA

An extension of HTCPCP protocol was published this week on IETF website. This new protocol is published in RFC 7168: "The Hyper Text Coffee Pot Control Protocol for Tea Appliances Efflux" (HTCPCP-TEA).  

This New RFC is available here: http://tools.ietf.org/html/rfc7168

The purpose of this extension is to allow service of tea. I do not approve this update at all. For me it is a sacrilege... especially in the morning. 

The teapot at www.error418.net is not yet compatible with the new protocol HTCPCP-TEA and will continue to issue 418 error. 

This new protocol can nevertheless be useful at five o'clock. An update of the teapot to make it compatible with the new protocol may be considered in the future.

One year of raspberry Pi power consumption

Oh my god! I missed my english version teapot anniversary post.

Power consumption was 1,7 kWh for december (and january and february)
.
Total power comsuption of the past year was 20,4 kWh.

I still have problem with my DNS, but i'm working on a new script

The return to a more reliable service has enabled 1,647 unique visitor went on the teapot on december, 2920 on january but only 502 on february beacause of big downtime issues.

The beginning of the year is also the time for accounting balance sheets, and here are the figures of the number of visits to different sites on the teapot.

	error418.org blog	error418.fr blog	error418.net teapot
January	366	394	867
February	448	347	945
March	635	369	1556
April	693	565	1384
May	833	765	1732
June	779	917	1272
July	786	1345	2473
August	644	617	1376
September	667	524	782
October	735	456	677
November	623	605	1537
Décember	648	1562	1647

For year 2014, I will continue to update my blogs with news about the teapot, but also other subjects. I renewed all my domains except 418error.net.

Fun with logs - Geeks

As promised, here is a small tribute to the geeks visiting the teapot!

The best query are received by me are those two. With HTCPCP protocol, url "coffee", BREW and PROPFIND methods and even a pot-designator!

In fact, I received  few comments, but the traces in the logs  attest to the visits of some purists  for the integration of HTCPCP.

So I must begin by apologizing. My implementation of HTCPCP protocol is probably not up to your expectations..

X.X.X.X - - [14/Mar/2013:15:40:12 +0000] "HTCPCP/1.0 coffee://error418.net/pot-1/ PROPFIND" 501 357 "-" "-"
X.X.X.X  - - [14/Mar/2013:15:42:00 +0000] "BREW coffee://error418.net/pot-1/ HTCPCP/1.0" 501 357 "-" "-"

There is occasionally some attempts to address the BREW method:
X.X.X.X - - [13/Mar/2013:20:19:34 +0000] "BREW / HTTP/1.1" 501 357 "-" "-"

X.X.X.X - - [06/Mar/2013:22:09:27 +0000] "BREW" 400 349 "-" "-"

X.X.X.X - - [17/Oct/2013:11:01:18 +0200] "BREW / HTTP/1.1" 501 357 "-" "-"

X.X.X.X - - [29/Jan/2013:18:28:54 +0000] "BREW / HTTP/1.0" 501 357 "-" "-"


Some uses of HTCPCP instead of HTTP
X.X.X.X - - [20/Nov/2013:17:44:33 +0100] "GET HTCPCP/1.1" 400 349 "-" "-"

X.X.X.X - - [24/Oct/2013:18:47:43 +0200] "BREW / HTCPCP/1.0" 501 357 "-" "-"

X.X.X.X - - [24/Nov/2013:21:38:15 +0100] "BREW coffee HTCPCP/1.0" 501 357 "-" "-"

X.X.X.X  - - [14/Mar/2013:15:40:54 +0000] "HTCPCP/1.0 pot-1 BREW" 501 357 "-" "-"

X.X.X.X  - - [14/Mar/2013:15:41:33 +0000] "BREW pot-1 HTCPCP/1.0" 501 357 "-" "-"


The POST method is also provided
X.X.X.X www.htcpcp.net - [02/Feb/2013:01:58:48 +0000] "POST / HTTP/1.1" 200 1371 "-" "curl/7.28.1"


Some PROPFIND requests
X.X.X.X error418.net - [17/Oct/2013:11:01:26 +0200] "PROPFIND / HTTP/1.1" 418 1370 "-" "curl/7.29.0"

X.X.X.X www.htcpcp.net - [13/Dec/2013:00:52:08 +0100] "GET /propfind HTTP/1.1" 404 345 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36"

A attempts cream parameter
X.X.X.X error418.net - [19/Mar/2013:18:29:03 +0000] "GET /BREW%20pot-1?cream;2 HTTP/1.1" 404 345 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22"

I would really like to tweak a nicer implementation HTCPCP. I have some ideas, but unfortunately not enough time to implement them a the moment. Modifying an open source HTTP server is the track that seems to me the easiest way to be able to support non-HTTP requests, and return a 418 error as expected for BREW HTCPCP an PRODFIN METHOD.