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.

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

http 1.1 message body (section 6) and get/head/delete semantics #1102

Open
daniel-white opened this issue Apr 12, 2023 · 1 comment
Open

Comments

@daniel-white
Copy link

I think theres a bit of an open loop hole in section 6 of http 1.1. #906 added the SHOULD NOT language to discourage the use of request bodies for get/head/delete methods. Section 6 states:

The presence of a message body in a request is signaled by a Content-Length or Transfer-Encoding header field.

Should the warnings be replicated or linked to here to reduce any confusion?

@royfielding
Copy link
Member

The warnings are not repeated here because the signal might occur anyway, and is dealt with accordingly. Messages need to be parsed based on these rules, so if the message indicates it has a body then it will be parsed as containing a body, even if that doesn't match the method semantics (which are enforced elsewhere).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants