SignatureV4 mismatch on some requests about aws-sdk-php

[GrahamCampbell]

This is likely because the encoding of the list parameters is not in a supported format. Try with:

https://[redacted].execute-api.eu-west-1.amazonaws.com/dev-ew1/api/v1/users?userId%5B0%5D=2405&userId%5B1%5D=196624&userType=student&oktaId=[redacted]

[GrahamCampbell]

(the difference being the encoding of the brackets and the use of 0 and 1 for the indices)

[IrisJasonStanley]

Thanks for taking the time to respond. Yesterday I was looking at how query string parameters were being encoded by the library and I was thinking that maybe there is a problem maintaining the order.

I had assumed that param[]=1&param[]=2 was part of the query string spec as this is how it is handled by PHP but now I read up on it I can see this is framework specific. I will change this up today and see if it resolved the problem

[IrisJasonStanley]

That has solved the issue. Adding multiple parameters with a [] prevents the requests from being signed in a consistent way. Thanks for your help with this.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[GrahamCampbell]

Yeh, there is "the query string spec", however in practice is is not followed to the letter. Many browsers and servers all do different things not in the spec. It's unfortunately pretty common (coming from someone who maintains an HTTP client). 😆

[stobrien89]

Thanks @GrahamCampbell,

I think this could be documented better. The closest thing I could find was this blog post from when they first introduced support for multi-value parameters. I'll reach out to the Api Gateway team and see if they're able to make this more visible in their developer guide.