Fix extra blank line when serializing empty header#145
Merged
kevinresol merged 1 commit intoJul 13, 2026
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Header.toString()appended two\r\nafter the (empty) field list, so a message with no header fields serialized with an extra blank line, e.g.GET / HTTP/1.1\r\n\r\n\r\n. Per RFC 7230 §3, the header section is terminated by a single empty line.The field block is now built as
field + CRLFper field followed by one terminatingCRLF, producingGET / HTTP/1.1\r\n\r\nfor empty headers while leaving messages that do have fields unchanged (they still end with a single blank line after the last field).Updated the
TestHeadervariants that asserted the old triple-CRLF empty-header form.Made with Cursor