Closed
Bug 774389
Opened 12 years ago
Closed 10 years ago
Override core exceptions to make it clear when the server is emitting them
Categories
(Cloud Services :: Server: Core, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: telliott, Assigned: rfkelly)
References
Details
(Whiteboard: [qa+])
When we emit a non-200 error, we should make sure the body has some sort of info that makes it clear that the python code itself has emitted the error (as opposed to zeus or nginx.). We do this for 400 and (I think) 503, but we should do it for 404, 412 and possibly others as well.
Updated•12 years ago
|
Whiteboard: [qa+]
Assignee | ||
Comment 1•12 years ago
|
||
What sort of information do you have in mind, and where will we be checking for this information? Is it for after-the-fact debugging from user error logs? It would be less ambiguous to flag this in a header, e.g. "X-Response-Originated-From: syncstorage" or something. But that would be less likely to show up in error logs.
Assignee | ||
Comment 2•10 years ago
|
||
sync-1.5 sends json with integer error codes for app-generated errors, I think we can close this out
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•