737057 - Content-type error on manifest is not properly propagated

Status: RESOLVED INVALID

(Web Apps :: HTML, defect)

Description

[Ian Bicking (:ianbicking)]

When you try to install an app with a manifest with the wrong content-type, /getmanifest just returns a 503 Bad Gateway error, and the error isn't reported properly in the API.

Comment 1

[Ian Bicking (:ianbicking)]

We'll need to formally define what /getmanifest should return in the case of a content-type mismatch

Comment 2

[Jason Smith [:jsmith]]

Maybe a HTTP Status Code 415?

415 Unsupported Media Type
    The request entity has a media type which the server or resource does not support.[2] For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.

Comment 3

[Ian Bicking (:ianbicking)]

I think 415 would indicate a bad *request*, and we're giving this error because the *response* would be of the wrong content-type.  503 isn't all bad, but we need to be more specific (e.g., include a particular header explaining the reason).