Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

codegen: Update REST streaming request payload content-type usage #360

Closed
wants to merge 1 commit into from

Conversation

jasdel
Copy link
Contributor

@jasdel jasdel commented Mar 17, 2022

Updates the SDK's codegen for REST HTTP request payload to always
include content-type header for operations with streaming request
payloads. Prior the content-type header would only be added if the
streaming request io.Reader was not nil.

Updates the SDK's codegen for REST HTTP request payload to always
include content-type header for operations with streaming request
payloads. Prior the content-type header would only be added if the
streaming request io.Reader was not nil.
@jasdel
Copy link
Contributor Author

jasdel commented Mar 23, 2022

This cannot be merged until aws/aws-sdk-go-v2#1630 failing test cases with content-type are fixed.

@jasdel jasdel marked this pull request as draft April 21, 2022 23:49
@jasdel jasdel closed this Jun 27, 2022
@jasdel jasdel deleted the updateSmithyTests branch June 27, 2022 17:34
jasdel added a commit that referenced this pull request Jun 28, 2022
Updates the SDK's codegen for REST HTTP request payload to always include content-type header for operations with streaming request payloads. Prior the content-type header would only be added if the streaming request io.Reader was not nil.

Also adds a helper utility for setting if the content-type was automatically assigned by the operation serializer or not. Used by behavior that needs to know if an explicit or default value was provided for the content-type header.

Replaces: #360
Used by: aws/aws-sdk-go-v2#1630
jasdel added a commit to aws/aws-sdk-go-v2 that referenced this pull request Jun 28, 2022
Updates the SDK's code generation of protocol test to no longer skip
tests for features that are supported by the SDK.

Regenerates SDK API clients for aws/smithy-go#360 and previously skipped protocol tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant