Closed
Bug 887872
Opened 11 years ago
Closed 11 years ago
OutdatedDataErrors shouldn't return a 500 error
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 922625
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [balrog])
Anything that causes an OutdatedDataError currently returns a 500 error. This isn't right because the server hasn't done anything wrong - the client simply lost a race. The annoying thing about this is that Sentry gets notified of each one of these without good reason. The client retries anyways, so these aren't really indicative of a problem. Looks like 409 ("Conflict") is the right thing to send.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Reporter | ||
Comment 1•11 years ago
|
||
In bug 922625 we started sending a 400 for them. 409 might be better, but it really doesn't matter in reality...
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•