RFC 2324 and 7168 define the COFFEE *AND* TEA pot control protocol, [dis]respectively
https://datatracker.ietf.org/doc/html/rfc7168 (note date of posting)
And, if you are a TEA pot and can not brew coffee (as a request may
specify) you would return a 418 error - "I'm a Teapot"
Currently it is reported that the Russian military's web site is
returning the 418 error...
https://www.theregister.com/2022/02/24/cyberwarfare_russia_ukraine/
"Russia's military website mil.ru is returning the joke HTTP 418 error
for those connecting from outside the nation."
I tried it uswing curl --verbose
https://mil.ru and got this:
GET / HTTP/1.1
Host: mil.ru
User-Agent: curl/7.79.1
Accept: */*
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 418
< Date: Fri, 25 Feb 2022 18:51:46 GMT
< Content-Length: 0
< Connection: keep-alive
< Server: Ministry of Defence of the Russian Federation
<
418 response. heh. (do you think this is a subtle way of the Russian
military to keep foreigners from accessing their server while
SIMULTANEOUSLY making a joke? Do you think that *MAYBE* they believe
that this ENTIRE INVASION is "nothing but a joke" ???
(they can not openly protest against it without severe consequences,
even in 2022. Putin does not tolerate dissent by Russian citizens, or
anyone inside his borders for that matter...)
--
(aka 'Bombastic Bob' in case you wondered)
'Feeling with my fingers, and thinking with my brain' - me
'your story is so touching, but it sounds just like a lie'
"Straighten up and fly right"
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)