Unmarshall response with blank object ("{}") and crc32 header

[voidresult]

Hello. We using SQS as service and has problem with exception "CRC value returned with response does not match the computed CRC...".
After analyses source code of AWSSDK.SQS I'm see next situation.
For example, when call SetQueueAttributesAsync, response contains empty object "{}" and has header "x-amz-crc32". As a result, calling of context.ValidateCRC32IfAvailable() throws exception, because SetQueueAttributesResponseUnmarshaller not call context.Read() and not initialize required fields.
And I would like to understand whether this is an implementation problem or whether this is incorrect behavior of the service providing SQS.

[dscpinheiro]

Did this start happening recently after you updated the SDK? I can't reproduce it using the latest version of the AWSSDK.SQS package.

Also, are you using a 3rd-party implementation? The SetQueueAttributes API always returns an empty response when successful, so there should be nothing to calculate a checksum for.

[voidresult]

Thanks by reply.
We use cloud platform that provide Message Queue service by SQS protocol. So i can't provide test example because the problem in response from API of that service.
I am get resonse with Content-Length = 2 and with crc32 header, that calls checksum validation. But marshaller implementation for this method not contains content processing. Checksum equals with zero value and throw exception about CRC error.
To reproduce this you need fake API response with crc32 header.
Now i am undestand that problem at service provider side.
But may be this error should be handled as "invalid response" instead of "checksum error".

[dscpinheiro]

Got it. Yes, it seems like a problem with the service not matching the SQS API, but for the record x-amz-crc32 is a legacy header that's only returned by DynamoDB if I remember correctly (it'll not be present for any other AWS services).