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

Clarify RPCv2 response event stream behavior #2297

Merged
merged 1 commit into from
Jun 3, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions docs/source-2.0/additional-specs/protocols/smithy-rpc-v2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -214,10 +214,10 @@ Buffered RPC requests for the ``rpcv2Cbor`` protocol SHOULD include a
``Content-Length`` header. Event streaming requests MUST NOT specify a content
length (instead using ``Transfer-Encoding: chunked`` on HTTP/1.1).

Event streaming requests for the ``rpcv2Cbor`` protocol MUST include an
``Accept`` header set to the value ``application/vnd.amazon.eventstream``.
Other forms of content streaming MAY be added in the future, utilizing
different values for ``Accept``.
Requests with event stream responses for the ``rpcv2Cbor`` protocol MUST
include an ``Accept`` header set to the value
``application/vnd.amazon.eventstream``. Other forms of content streaming MAY be
added in the future, utilizing different values for ``Accept``.

In summary, the ``rpcv2Cbor`` protocol defines behavior for the following
headers for requests:
Expand All @@ -242,7 +242,8 @@ headers for requests:
For event streaming requests, this MUST NOT be set.
* - ``Accept``
- Conditional
- For event streaming requests, to the value ``application/vnd.amazon.eventstream``.
- For requests with event streaming responses, this is
``application/vnd.amazon.eventstream``.


~~~~~~~~~
Expand Down
Loading