Closed
Bug 773073
Opened 12 years ago
Closed 12 years ago
don't send stringified exceptions to the client
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Assigned: rfkelly)
References
Details
(Whiteboard: [qa+])
Attachments
(1 file)
994 bytes,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
server-syncstorage controller.py currently does this: try: modified = storage.set_items(user_id, collection_name, kept_bsos) except Exception, e: # Something went wrong. # We want to swallow the 503 in that case. self.logger.error('Could not set items') self.logger.error(str(e)) for bso in kept_bsos: res['failed'][bso['id']] = str(e) It is a bad idea to be sending stringified errors back to the client. We should log it, then send back a generic error message. Also need to audit the code for other instances of this.
Updated•12 years ago
|
Whiteboard: [qa+]
Assignee | ||
Comment 1•12 years ago
|
||
Replace the stringified exception with a short generic message. grep reveals no other locations where stringified exceptions might be leaking through.
Attachment #646816 -
Flags: review?(telliott)
Updated•12 years ago
|
Attachment #646816 -
Flags: review?(telliott) → review+
Assignee | ||
Comment 2•12 years ago
|
||
Committed in sync1.1 and sync2.0: http://hg.mozilla.org/services/server-storage/rev/9d341cf08df5 https://github.com/mozilla-services/server-syncstorage/commit/08482406ef1670b9c8be1bef886b0e5920b8c63a
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 3•12 years ago
|
||
Will verify this against Sync 1.1 and 2.0.
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•