You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thank you for this wonderful library!
I've been using it to communicate with the SES API, specifically the get_identity_verification_attributes call, and it seems that current body encoder is not handling certain requests in accordance with the spec.
First of all thank you for this wonderful library!
I've been using it to communicate with the SES API, specifically the
get_identity_verification_attributes
call, and it seems that current body encoder is not handling certain requests in accordance with the spec.The call:
generates following request body:
This results in a HTTP 400 from AWS, which happens due to the array member naming convention of having the "member" in between the array name and the index:
Identities.member.1=example.com
rather thanIdentities.1=example.com
. (See https://docs.aws.amazon.com/ses/latest/APIReference/API_GetIdentityVerificationAttributes.html)AWS CDK for e.g. Golang factors in the member name in the array format (https://github.com/aws/aws-sdk-go-v2/blob/main/aws/protocol/query/array.go#L36), and I assume the
AWS.Util.encode_query_value/1
would need to be made configurable to some extent to allow those member names globally/per API.I'll do more research on this convention and gladly raise a PR to address this issue - suggestions are welcome.
The text was updated successfully, but these errors were encountered: