Content-type error on manifest is not properly propagated

RESOLVED INVALID

Status

Web Apps
HTML
RESOLVED INVALID
6 years ago
3 years ago

People

(Reporter: ianbicking, Assigned: ianbicking)

Tracking

Details

(Assignee)

Description

6 years ago
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.
(Assignee)

Comment 1

6 years ago
We'll need to formally define what /getmanifest should return in the case of a content-type mismatch
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.
(Assignee)

Comment 3

6 years ago
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).

Updated

6 years ago
Whiteboard: [marketplace-beta?]

Updated

6 years ago
Whiteboard: [marketplace-beta?]
(Assignee)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.