Chunked error responses not correctly parsed?

[DetlefGolze]

I don't want to make this a bug report right now, because I don't have the time to look at the source code to verify that my observation is correct. But maybe someone knows the code or has seen similar behaviour. Thanks.

I'm using an S3 store which returns error responses as chunked transfer and it seems like the SDK does not parse this correctly. In this case I am querying ACL of a bucket which is not allowed. The store responds with 403 and the following error response:

But the exception looks like this:

StatusCode: Forbidden
ErrorCode: Forbidden
Message: Error making request with Error Code Forbidden and Http Status Code Forbidden. No further error information was returned by the service.

Obviously the error response is not parsed and the HTTP status is used as only information. The only difference to other stores, that I can find, is the chunked transfer of the response data.

Note that AWS CLI correctly reports ErrorCode "AccessDenied" so that I conclude that the response cannot be so bad. Also, this store is from a big manufacturer and there is little chance to tell them to change this.

[DetlefGolze]

I had the time to step through the code and found that the S3ErrorResponseUnmarshaller fails if the Content-Type header contains a character set like this:
Content-Type: application/xml;charset=utf-8
The error response is only parsed if the content type ends with "/xml".

I'll close this and will file a bug report and eventually provide a fix. Thanks.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.