Cloud9 `NotFoundException` deserialization error about aws-sdk-go-v2 HOT 3 CLOSED

Hi @ewbankkit ,

Thanks for reaching out. I logged the raw response before it gets deserialized by the SDK and it looks like this:

SDK 2024/02/06 11:28:52 DEBUG Response
HTTP/2.0 400 Bad Request
Content-Length: 123
Content-Type: application/x-amz-json-1.1
Date: Tue, 06 Feb 2024 19:28:52 GMT
X-Amzn-Requestid: REDACTED

{"__type":"NotFoundException","className":"NotFound","code":404,"message":"Unable to find [nonExistentEnvId] in database."}

As you can see, two separate sets of errors are being sent, one in the headers and one in the body. Based on the JSON protocol cloud9 uses, the error code should be only specified in the header (string) whereas the service models their code field as an integer as shown in the body.

I'll raise this internally and see how we can address this.
Thanks again,
Ran~

from aws-sdk-go-v2.

The root cause here is that we're making the incorrect assumption that code is a special field in awsjson errors meant to hold the modeled error's name. This is true for __type but the former can technically be modeled as one of the members on the error as well. We're not accounting for that, which we'll need to fix.

from aws-sdk-go-v2.

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from aws-sdk-go-v2.