Add autest for empty POST framing: 411 response#13055
Merged
bneradt merged 1 commit intoapache:masterfrom Apr 3, 2026
Merged
Conversation
Add a replay-based autest for a POST request that omits both Content-Length and Transfer-Encoding. This captures the current 411 response in ATS and gives us a focused reproducer for issue 12960. 411 is in compliance with the RFC: https://datatracker.ietf.org/doc/html/rfc9112#section-6.3 A server MAY reject a request that contains a message body but not a Content-Length by responding with 411 (Length Required). Fixes: apache#12960
masaori335
approved these changes
Apr 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add a replay-based autest for a POST request that omits both
Content-Length and Transfer-Encoding. This captures the current
411 response in ATS and gives us a focused reproducer for issue
12960.
411 is in compliance with the RFC:
https://datatracker.ietf.org/doc/html/rfc9112#section-6.3
A server MAY reject a request that contains a message body but not a
Content-Length by responding with 411 (Length Required).
Fixes: #12960