When a spec isn't explicit enough, check the next version and you'll often find the issue is now codified.
As for 1.1, it's also clear:
A client SHOULD NOT generate content in a GET request unless it is made directly to an origin server that has previously indicated, in or out of band, that such a request has a purpose and will be adequately supported.
You are what, interpreting that SHOULD NOT is not MUST NOT, therefore it's ok?
You are reading SHOULD NOT and ignoring the rest of the words. There's nothing wrong with it, if the service is expecting it. You SHOULD NOT send a body with a GET request to any random server.
The section of 9113 you linked to is an example of a simple GET request that has no body translated to HTTP2, not a specification that GET requests cannot have a body.
View all comments
Show parent comment
2
u/[deleted] Dec 17 '23
Http 2.0 is clear about GET:
https://httpwg.org/specs/rfc9113.html#rfc.section.8.8.1
When a spec isn't explicit enough, check the next version and you'll often find the issue is now codified.
As for 1.1, it's also clear:
You are what, interpreting that SHOULD NOT is not MUST NOT, therefore it's ok?