Specify supported media types when sending "415 unsupported media type"

http rest http-status-codes httpresponse content-negotiation
deamon picture deamon · Jul 27, 2010 · Viewed 11.8k times · Source

If a clients sends data in an unsupported media type to a HTTP server, the server answers with status "415 unsupported media type". But how to tell the client what media types are supported? Is there a standard or at least a recommended way to do so? Or would it just be written to the response body as text?

Answer

Donal Fellows picture Donal Fellows · Jul 27, 2010

There is no specification at all for what to do in this case, so expect implementations to be all over the place. (What would be sensible would be if the server's response included something like an Accept: header since that has pretty much the right semantics, if currently in the wrong direction.)

Related questions

Should I return a 401 or a 405 response code to a REST API user without sufficient access?

I'm developing an API which will also have an authentication/authorization component. Anybody, regardless of authentication status, will be able to write (POST), but depending on if you are unauthenticated, authenticated as a normal user or authenticated as an admin …

Read More
Most appropriate HTTP status code for "job in progress"

What is the most appropriate HTTP status code to give to a client to mean "your request is fine, but it is still in progress; check back shortly in the exact same place." For example, say the client submits an …

Read More
REST HTTP status codes for failed validation or invalid duplicate

I am building an application with a REST-based API and have come to the point where I am specifying status codes for each requests. What status code should i send for requests failing validation or where a request is trying …

Read More