If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Handle 413 responses correctly

VERIFIED WONTFIX

Status

Web Apps
AppsInTheCloud
VERIFIED WONTFIX
5 years ago
3 years ago

People

(Reporter: anant, Assigned: rfkelly)

Tracking

Details

(Whiteboard: [blocking-aitc-])

(Reporter)

Description

5 years ago
We currently simply remove an app from the queue if we receive a 413 response from the server. There's probably something better to be done here.
(Reporter)

Comment 1

5 years ago
This seems like something we need to log on the server side (reporting API?), because 413s mean something is really wrong!
Assignee: nobody → rfkelly

Updated

5 years ago
Whiteboard: [blocking-aitc-]
(Assignee)

Comment 2

5 years ago
Indeed, we will eventually have structured logging for (almost?) all non-200 error codes - Bug 760355.
Blocks: 760355
Whiteboard: [blocking-aitc-] → [blocking-aitc-][qa+]
I'd hold off on flagging qa+ until the patch is heading to land (cause that's the time when the parameter matters).
Whiteboard: [blocking-aitc-][qa+] → [blocking-aitc-]
(Assignee)

Comment 4

3 years ago
AitC LOL, we don't need this no more.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
OK.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.