docs: returned header size reflects HTTP/1-style format#21912
Closed
vszakats wants to merge 4 commits into
Closed
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the CURLINFO_HEADER_SIZE documentation to clarify that the reported header size corresponds to libcurl’s HTTP/1-style textual header representation, which is particularly relevant when using HTTP/2+ where on-the-wire header bytes differ due to framing/compression.
Changes:
- Clarify that headers are measured in an HTTP/1-style textual format rather than raw on-the-wire bytes.
- Add a note that HTTP/2+ wire/TLS-layer byte counts differ from the reported value.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
bagder
approved these changes
Jun 9, 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
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.
Ref: #21889