Handle 413 responses correctly

VERIFIED WONTFIX

Status

VERIFIED WONTFIX
7 years ago
2 months ago

People

(Reporter: anant, Assigned: rfkelly)

Tracking

Details

(Whiteboard: [blocking-aitc-])

(Reporter)

Description

7 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

7 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
Whiteboard: [blocking-aitc-]
(Assignee)

Comment 2

7 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

5 years ago
AitC LOL, we don't need this no more.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
OK.
Status: RESOLVED → VERIFIED

Updated

2 months ago
Product: Web Apps → Web Apps Graveyard
You need to log in before you can comment on or make changes to this bug.