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

Add Support for Lex Runtime V2 StartConversation API. #1515

Merged
merged 3 commits into from
Dec 2, 2021

Conversation

skmcgrail
Copy link
Member

Verified the API supports the Expect 100-continue client behavior.

@skmcgrail skmcgrail requested a review from jasdel December 1, 2021 23:01
@skmcgrail skmcgrail merged commit c98c939 into aws:main Dec 2, 2021
@skmcgrail skmcgrail deleted the lexgen branch December 2, 2021 00:35
jrichard8 pushed a commit to jrichard8/aws-sdk-go-v2 that referenced this pull request Feb 14, 2022
jasdel added a commit to jasdel/aws-sdk-go that referenced this pull request Feb 21, 2022
Adds fix addressing an issue where SDK's bi-directional eventstream API
operation request could hang when the HTTP/2 stream was closed by the
service with a non-200 status code.

Go 1.15 through 1.17 have an issue where the HTTP/2 request can hang
while waiting for the HTTP response, and input payload reader. The
Expect: 100-Continue workaround forces the HTTP client to wait for a
`100 continue` or other HTTP status code before attempting to wait for
the request's body to be read. This workaround is not needed for Go
1.18, as a fix to the HTTP client resolves this issue.

Related to aws/aws-sdk-go-v2#1515
jasdel added a commit to aws/aws-sdk-go that referenced this pull request Feb 22, 2022
…#4288)

Adds fix addressing an issue where SDK's bi-directional eventstream API
operation request could hang when the HTTP/2 stream was closed by the
service with a non-200 status code.

Go 1.15 through 1.17 have an issue where the HTTP/2 request can hang
while waiting for the HTTP response, and input payload reader. The
Expect: 100-Continue workaround forces the HTTP client to wait for a
`100 continue` or other HTTP status code before attempting to wait for
the request's body to be read. This workaround is not needed for Go
1.18, as a fix to the HTTP client resolves this issue.

Related to aws/aws-sdk-go-v2#1515
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.

2 participants