Live data from Hacker News

HTTP Status 418 I'm a teapot

en.wikipedia.org

1–10 of 34 posts

Re: HTTP Status 418 I'm a teapot

#3
post #2

Does anyone have any idea where in the HTTP headers we would store whether the teapot was Short and/or Stout?

Since we're talking about the Hyper Text Coffee Pot Control Protocol here, physical attributes of the teapot are irrelevant and thus outside of the scope of the RFC.

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

#8
post #5
post #4

Some 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.

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

#9
post #8
post #5

Earlier 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.

I would not risk depleting my home network address pool either. What if I want to connect 4 billion + 1 washing machines?
Post reply on HN