vote: status codes (was Re: [gcs-pcs-list] (possible) issue: what to do for redirects?)

[Rob Sanderson]

On Wed, 2006-03-08 at 17:02 +0000, Leigh Dodds wrote:

> >    * 415 Unsupported Media Type - requests for a URI that is available
> >    on the server but for a format that is not available for that URI
> 
> 415 isn't really suitable here. It's for use when the server is
> "refusing to service the request because the entity of the request is
> in a format not supported by the request resource for the requested
> method". There's no entity being sent here.

Isn't the 'entity' here the object identified by the URI?

eg, one description I quickly found:

Your Web server thinks that the HTTP data stream sent by the client
identifies a resource whose actual media type 1) does not agree with the
media type specified on the request or 2) is incompatible with the
current data for the resource or 3) is incompatible with the HTTP method
specified on the request.

The media type in the request (by the format param) is not compatible
with the object identified (by the URI param).


Which is countered by a second description equally quickly found:

This code is returned when a server refuses a request because the
message body is in an inappropriate format.

Which talks explicitly about the message body.

I guess that's the downside with using HTTP error codes for non HTTP
errors!

Rob