Resolve 400 vs 415

[jpstroop]

We should be more explicit about the 415 in section 4.5 if we think it's important to distinguish from other 400 errors codes. As just .../native is okay, and the server can do conneg, then 415 actually isn't the right error code, it should be 406 Not Acceptable.
Maybe we include a flowchart if we want to maintain the distinctions

Current: 415 - Format not supported
Alternatives: 406?
What about Conneg - 406 for that?
Spec says you may always return an image, even if in a different format.

[jpstroop]

See:

https://github.com/IIIF/specifications/blob/master/image_api/image_api_1.2.md#45-format

We worked on this in Copenhagen and decided to drop all 4xx language from this part of the spec. In 6.2 we added:

406 Not Acceptable | The server does not support the format requested by Content Negotiation. If the requested format is specified in the URI, and the server is not able to deliver it, then the appropriate error code is 400.

[zimeon]

+1

[azaroth42]

+1

On Thu, Feb 27, 2014 at 7:50 AM, Simeon Warner notifications@github.comwrote:

+1

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-36248820
.