W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

p1: generating "internal" errors

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 20 Apr 2013 14:07:52 +1000
Message-Id: <EA721AC2-5655-4EC6-851B-303EE22BB670@mnot.net>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
p1 3.2.4 requires that a syntax violation in a received response be turned into a 502 (Bad Gateway) status code.

I'm not necessarily against it, but I think if we're going to take this approach to errors in received responses, it should be systematic, and we should recommend that others do it too. Currently, a lot of people are inventing new pseudo status codes to fill this role.

What do people think?

This might not result in any changes in our specs beyond adjusting language in a few other places to do the same thing. I could see writing a separate spec for a header that described the type of error, though.


--
Mark Nottingham   http://www.mnot.net/
Received on Saturday, 20 April 2013 04:08:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC