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.

Sign up for GitHub

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

Jump to bottom

Defining Content-Length independently from its use in HTTP/1.1 framing #118

Closed
royfielding opened this issue Jul 2, 2018 · 1 comment · Fixed by #433
Closed

Defining Content-Length independently from its use in HTTP/1.1 framing #118

royfielding opened this issue Jul 2, 2018 · 1 comment · Fixed by #433
Assignees
@royfielding
Labels
has-proposal semantics

Comments

@royfielding
Copy link
Member

We decided to move the version-independent parts of the definition of Content-Length to Semantics, but that calls for some new text to explain its semantics in general.

For now, we have added (in crefs) the following text to the section on "Content-Length" in Semantics:

The "Content-Length" header field indicates the number of data octets (body length) for the representation. In some cases, Content-Length is used to define or estimate message framing.
@mnot
Copy link
Member

mnot commented Oct 9, 2018

s/representation/representation data/?

@mnot mnot mentioned this issue Mar 19, 2020
Closed
@royfielding royfielding mentioned this issue Aug 7, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@royfielding royfielding

Labels
has-proposal semantics
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Define Content-Length independently from its use in HTTP/1.1 framing httpwg/http-core
2 participants
@mnot @royfielding