doc: fix example of content-length to correct value#43361
doc: fix example of content-length to correct value#43361hamishwillee merged 5 commits intomdn:mainfrom
Conversation
aa76088 to
e95d9e7
Compare
|
Preview URLs (2 pages) (comment last updated: 2026-03-08 23:44:34) |
There was a problem hiding this comment.
I find this sentence strange because the server can generate content-length: 0, as is the example in line 47 below.
RFC 9110 15.3.6. 205 Reset Content
Since the 205 status code implies that no additional content will be provided, a server MUST NOT generate content in a 205 response.
Perhaps @hamishwillee could take a look at how to rephrase this sentence, thank you.
There was a problem hiding this comment.
The spec says "should not". I'll patch this here. Thanks.
A user agent SHOULD NOT send a Content-Length header field when the request message does not contain content and the method semantics do not anticipate such data.
Josh-Cena
left a comment
There was a problem hiding this comment.
I think you should replace ! with %21 and set the length to 16 since it's application/x-www-form-urlencoded.
Yes, you are right. Thanks ! |
Clarified response content requirements for 205 status code.
hamishwillee
left a comment
There was a problem hiding this comment.
Thanks very much @samuel871211 (and @Josh-Cena )
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Description
Motivation
Additional details
Related issues and pull requests