Description
Any attempt to brew coffee with a teapot should result in the error code “418 I’m a teapot”. The resulting entity body MAY be short and stout.
Usage: Activate and visit http://example.com/brew
Reviews
April 7, 2017
1 reply
Thank you, Steven, for finally adding status header 418 to WordPress!
I’m not entirely convinced yet that this HTCPCP implementation fully conforms to RFC 2324 specifications, though. 😉 For example, it might be desirable to handle response cases a little less strictly overall.
Perhaps you might wish to consider something along the line of Google’s Teapot (tying the response header to the request URL, that is), which I think would run less of a risk of putting off users who didn’t try to brew coffee with a teapot.
It would be really nice to see this implemented before next April 1st!
Contributors & Developers
“WP Teapot” is open source software. The following people have contributed to this plugin.
Contributors
“WP Teapot” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “WP Teapot” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.2
- WordPress version 5.9 compatibility
1.0.1
- Less aggressive on the take over. Now only serves out of /brew
- Borrows Google’s 418 page.