Smithy is a protocol-agnostic interface definition language and set of tools for generating clients, servers, and documentation for any programming language.
Add protocol tests relating to Content-Type and @httpPayload
Initial motivation for this stems off #2310, but for when the input is
@httpPayload-bound. It's important that we test Content-Type
specifically with @httpPayload operations, because the header can be
checked without having to inspect the body, and because the spec has
special provisions
(https://smithy.io/2.0/aws/protocols/aws-restjson1-protocol.html#content-type).
There were no protocol tests exercising Content-Type when the input is
@httpPayload-bound:
In the case of blobs, servers must accept any (test already exists)
and no Content-Type (test added in this commit).
In other cases, there were protocol tests for union and structure
shapes. I've added an operation with an @httpPayload-bound string
shape. Note that document shapes remain untested.
Testing
Ran tests against smithy-rs servers.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Add protocol tests relating to
Content-Typeand@httpPayloadInitial motivation for this stems off #2310, but for when the input is
@httpPayload-bound. It's important that we testContent-Typespecifically with@httpPayloadoperations, because the header can be checked without having to inspect the body, and because the spec has special provisions (https://smithy.io/2.0/aws/protocols/aws-restjson1-protocol.html#content-type).There were no protocol tests exercising
Content-Typewhen the input is@httpPayload-bound:Content-Type(test added in this commit).unionandstructureshapes. I've added an operation with an@httpPayload-bound string shape. Note thatdocumentshapes remain untested.Testing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.