fix: populate content-type header for all event messages #3760
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Associated with: smithy-lang/smithy-typescript#567
Ref: P66766800
Description
Populate the
:content-type
header for all the event messages. It was missed previously. When the payload shape isblob
, the value isapplication/octet-stream
; When the payload shape isstring
, the value istext/plain
, When the payload shape isUnion
orStructure
, the value is the protocol's content type.Testing
automated integration test
Manual test, automated integration test not added because it relies on other client to spin up resources. Will create follow-up item.
Additional context
Add any other context about the PR here.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.