Opened at 2011-11-19T02:38:01Z

Last modified at 2016-06-28T18:17:14Z

#1589 closed defect

S3 backend: when a txaws operation gets an error response, include the full request URI and response body in the exception message, and maybe trigger an incident — at Version 1

Reported by: davidsarah Owned by:
Priority: major Milestone: 1.14.0
Component: code-storage Version: 1.9.0-s3branch
Keywords: error s3-backend txaws reviewed Cc: zooko
Launchpad Bug:

Description (last modified by davidsarah)

The exception message shouldn't include secrets (AWS secret key, user token or product token), or data, but the request URI and the body of error responses are short enough to include in full. In particular the response code, which txaws currently drops, would be useful. We don't send any caps in S3 requests.

It would also be useful to trigger an incident for errors that we don't understand or haven't seen before (probably based on the HTTP response code).

Change History (1)

comment:1 Changed at 2011-11-19T16:30:53Z by davidsarah

  • Description modified (diff)
  • Summary changed from S3 backend: when a txaws operation gets an error response, include the full request URI and response body in the exception message to S3 backend: when a txaws operation gets an error response, include the full request URI and response body in the exception message, and maybe trigger an incident
Note: See TracTickets for help on using tickets.