On Dec 10, 2007, at 6:05 AM, Julian Reschke wrote:
I think my bottom line is the same as Boris's, I would like to see
the spec allow XHR implementations not to send GETs with an entity-
body.
I would argue that both the simplest thing and the right thing here
is not to state anything at all, and let RFC2616bis clarify.
1) The RFC will only clarify the protocol issues (whether a GET
request is allowed to have a body). I don't think that automatically
specifies the behavior at the XMLHttpRequest API level. In particular
if the RFC does not allow some kinds of requests to have a body, that
doesn't define what should happen if you client code tries to include
one anyway (exception? silently ignored? sent anyway? implementation-
defined?). And conversely, if the RFC treats some set of things
without special-casing, that doesn't automatically mean XHR can't
special-case anyway, for example it special-cases a number of request
headers already.
2) We could probably make up spec language that specifies this in
terms of whatever the RFC ends up saying, but it would be pretty
convoluted.
3) The spec as written doesn't "state nothing", it appears to clearly
require sending an entity body and does not allow ignoring the body or
throwing an exception regardless of what is allowed per RFC. So some
change is needed, one way or another.
Regards,
Maciej
