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

fix(middleware-content-length): swallow error if content-length computation fails #3429

Merged

Conversation

trivikr
Copy link
Member

@trivikr trivikr commented Mar 15, 2022

Issue

Fixes: #3418

Description

Switches back to previous experience where header 'content-length' was not set, and no other header was set.

The existing behavior was added after checking RFC 7230 in #3400 (comment), and AWS SDK for Python behavior in #3400 (comment). The issue happened in Transcribe Streaming as it uses HTTP/2, and the middleware doesn't check for version of HTTP protocol for setting 'transfer-encoding' header.

Testing

Unit tests are absent, and to be added separately to the module.
No additional testing needed, as it's basic reverting to the previous flow.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@trivikr trivikr requested a review from a team as a code owner March 15, 2022 20:29
@trivikr trivikr changed the title fix(middleware-content-length): do not set transfer-encoding if content-length computation fails fix(middleware-content-length): swallow error if content-length computation fails Mar 15, 2022
@trivikr trivikr merged commit 8c12233 into aws:main Mar 15, 2022
@trivikr trivikr deleted the transfer-encoding-header-transcribe-streaming branch March 15, 2022 20:46
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[REG 3.53->3.54] HTTP/1 Connection specific headers are forbidden: "transfer-encoding"
2 participants