[tahoe-lafs-trac-stream] [tahoe-lafs] #2116: xml parse error from S4 service

[tahoe-lafs]

#2116: xml parse error from S4 service
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  daira
         Type:  defect   |     Status:  assigned
     Priority:  major    |  Milestone:  undecided
    Component:  code-    |    Version:  1.9.0-s3branch
  storage                |   Keywords:  s3 error txaws retry LeastAuthority
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by daira):

 Replying to [comment:16 daira]:
 > Note that the error occurs in txAWS when it tries to parse an empty
 response body for a 500 error as XML.

 No, this is a wrong inference. The error occurs in
 `txaws.s3.client._parse_get_bucket`, which should not be reached if the S3
 server responded with a 500 error. (The 500 error in the stack trace is
 from the Tahoe-LAFS gateway, not S3.) So it looks like S3 returned success
 with an empty body.

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