Fix iotsecuretunneling and mobile API clients to use correct signing name #1711
Conversation
Updates the API models the SDK uses to pull in changes that were not included in automated releases. iotsecuretunnling and mobile model updates fix aws#1686 where the request was being signed with the wrong name.
| "http": ["http/1.1", "h2"], | ||
| "eventStreamHttp": ["h2"] |
There was a problem hiding this comment.
These are new to the trait, wonder if there is any guidance on how we should use them.
There was a problem hiding this comment.
Looks like they are documented on the protocols. Basically the priority order of the HTTP protocol version used. eventStreamHttp basically stating only h2 should be used. The v1 SDK models had similar ideas, but I think it was in the metadata section. The AWS SDK for Go never really used these traits since h2 is handled so transparently by the HTTP client.
Each entry in http and eventStreamHttp SHOULD be a valid Application-Layer Protocol Negotiation (ALPN) Protocol ID (for example, http/1.1, h2, etc). Clients SHOULD pick the first protocol in the list they understand when connecting to a service. A client SHOULD assume that a service supports http/1.1 when no http or eventStreamHttp values are provided.
Fixes iotsecuretunneling and mobile API clients to use the correct name for signing requests. The models for these APIs contained the wrong name. This PR fixes that, and regenerates the API clients.
Fixes #1686.