![]() ![]() He just wanted to clarify 418's status - or lack thereof. Nottingham wasn't expecting such a big response, he told Business Insider. ![]() That scored technical points for Brunswick's side. Others pointed out that the teapot status has been treated as a part of HTTP for so long that removing it could actually cause technical problems for many sites. " It’s a reminder that the underlying processes of computers are still made by humans," Brunswick said. It's a silly little thing from the early internet that's worth preserving, he said. The teapot error is something "that puts a smile on your face," Brunswick told Business Insider. Brunswick, who will be a sophomore in high school this fall, started a "Save 418" movement, giving it the #Save418 hashtag. The biggest champion of the teapot status was 15-year-old programmer Shane Brunswick. Fortunately, this story has a happy ending. This prompted a swift, but fiery, debate of the future of the web's teapot error code. " I know it's amusing, I know that a few people have knocked up implementations for fun, but it shouldn't pollute the core protocol," Nottingham wrote. People should stop treating 418 as a core part of the HTTP standard, and free up the error number for more serious concerns, he said in his post. In a GitHub thread, Mark Nottingham, the chairman of the IETF working group that oversees hypertext transfer protocol (HTTP), argued that the 418 error was never a part of the standard, which governs how web browsers communicate with web servers. ![]() On Thursday, however, the future of code 418 was briefly called into doubt. Someone even rigged a teapot to act as a web server, just so it can proudly display error 418 when you visit it. Programming languages like Node.js and Google's Go both include the 418 error as a little Easter egg, as does Microsoft's ASP.NET framework. The error code has since become a running gag. If it sounds like a joke, it is: Way back on April Fool's Day in 1998, a wag proposed that the Internet Engineering Task Force (IETF) - a group that sets internet standards - adopted " a protocol for controlling, monitoring, and diagnosing coffee pots." That document defined status 418 thusly: "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." ![]() Less commonly spotted is error code 418, which makes your browser proclaim "I'm a teapot." You've likely seen numbers 404 ("not found") or 403 ("forbidden"). If you've spent any time browsing the web, chances are pretty good you've run into a page with an error code on it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |