Closed Bug 760911 Opened 13 years ago Closed 11 years ago

Handle 413 responses correctly

Categories

(Web Apps Graveyard :: AppsInTheCloud, defect)

Product:
Web Apps Graveyard
Component:
AppsInTheCloud
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: anant, Assigned: rfkelly)

References

Details

(Whiteboard: [blocking-aitc-])

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
Whiteboard: [blocking-aitc-]
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-]
AitC LOL, we don't need this no more.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
OK.
Status: RESOLVED → VERIFIED
Product: Web Apps → Web Apps Graveyard
You need to log in before you can comment on or make changes to this bug.