- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 31 Jan 2015 15:33:47 +0100
- To: ietf-http-wg@w3.org
Hi there, the minutes (<http://tools.ietf.org/wg/httpbis/minutes?item=minutes-90-httpbis.html>) say: > Ted: Has concern when this might appear in other places. Semantics > are clearer > if it comes in 4xx, confusing if in 2xx (but possibly valuable). Prefers a > different status code Ted: 1) What exactly are your concerns with respect to use in status codes other than 4xx? 2) Regarding another status code: this is not new; RFC 7231 already says that 415 is applicable to unsupported content encodings (<http://greenbytes.de/tech/webdav/rfc7231.html#status.415>): > 6.5.13 415 Unsupported Media Type > > The 415 (Unsupported Media Type) status code indicates that the origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource. The format problem might be due to the request's indicated Content-Type or Content-Encoding, or as a result of inspecting the data directly. Why do you think that a new status code is needed here? Best regards, Julian
Received on Saturday, 31 January 2015 14:34:27 UTC