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.
This seems like something we need to log on the server side (reporting API?), because 413s mean something is really wrong!
Assignee: nobody → rfkelly
Indeed, we will eventually have structured logging for (almost?) all non-200 error codes - Bug 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-]
AitC LOL, we don't need this no more.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.