[tahoe-lafs-trac-stream] [tahoe-lafs] #1589: 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 (was: S3 backend: when a txaws operation gets an error response, include the full request URI and response body in the exception message)

[tahoe-lafs]

#1589: 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
------------------------------+------------------------------------
     Reporter:  davidsarah    |      Owner:
         Type:  defect        |     Status:  new
     Priority:  major         |  Milestone:  1.10.0
    Component:  code-storage  |    Version:  1.9.0b1
   Resolution:                |   Keywords:  error s3-backend txaws
Launchpad Bug:                |
------------------------------+------------------------------------
Description changed by davidsarah:

Old description:

> 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.

New description:

 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).

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1589#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage