HTTP Status 418 I'm a teapot
en.wikipedia.org
HTTP Status 418 I'm a teapot
1–10 of 34 posts
Re: HTTP Status 418 I'm a teapot
#2Re: HTTP Status 418 I'm a teapot
#3Does anyone have any idea where in the HTTP headers we would store whether the teapot was Short and/or Stout?
The RFC (http://www.ietf.org/rfc/rfc2324.txt) specifically states:
2.3.2 418 I'm a teapot
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.Re: HTTP Status 418 I'm a teapot
#4Re: HTTP Status 418 I'm a teapot
#5Some day, when your fridge, oven, and yes, teapot all have IP addresses, this will finally come into its own.
Re: HTTP Status 418 I'm a teapot
#6Some day, when your fridge, oven, and yes, teapot all have IP addresses, this will finally come into its own.
Re: HTTP Status 418 I'm a teapot
#7http://www.id3.org/id3v2.3.0#head-70a65d30522ef0d37642224c2a...
Re: HTTP Status 418 I'm a teapot
#8Some day, when your fridge, oven, and yes, teapot all have IP addresses, this will finally come into its own.
as long as they use IPv6.
Re: HTTP Status 418 I'm a teapot
#9Earlier quoted context omitted.
as long as they use IPv6.
They won't need to, there's plenty of space in the private range in IPv4 to put everything in my house on the net. IPv6 isn't going to make firewalls and private networks go away, people aren't going to just put everything directly on the Internet with a public IP just because they can just as no one gives every PC on their network now live IP's.
Re: HTTP Status 418 I'm a teapot
#10Some day, when your fridge, oven, and yes, teapot all have IP addresses, this will finally come into its own.
http://www.embeddedarm.com/software/arm-netbsd-toaster.php
NetBSD really does run on everything.