Closed
Bug 664411
Opened 15 years ago
Closed 15 years ago
Provide a crash id to the client on server crash
Categories
(Cloud Services :: Server: Core, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tarek, Assigned: tarek)
Details
Attachments
(1 file)
|
6.04 KB,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
On any 503, the server logs the traceback on the server and returns an empty body --for security reasons--, instead we should return a unique id the client is able to give us in a bug entry, for us to find in the server(s) logs
Proposal for the body:
"application error: crash id 7a28ca56541418ea83052ff4b275de60"
The traceback logged will be prefixed by this hash
| Assignee | ||
Comment 1•15 years ago
|
||
Notice that the response sent is a json string.
| Assignee | ||
Updated•15 years ago
|
Summary: Provide useful information on server crash → Provide a crash id to the client on server crash
When this is deployed, we'll need to adjust certain aspects of the Zeus to maintain the application-provided body when an error occurs. Currently it does not.
| Assignee | ||
Comment 3•15 years ago
|
||
Comment 4•15 years ago
|
||
Comment on attachment 539499 [details] [diff] [review]
Adds a crash id feature
Code looks fine, but we need to make sure that both Zeus and the client aren't looking for a particular string in the response before we deploy this.
Attachment #539499 -
Flags: review?(telliott) → review+
rnewman and i have confirmed that neither the Zeus nor the client care at all what is in the body of a 5xx error response. this statement applies *only* to 5xx error responses.
| Assignee | ||
Comment 6•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•