Re: [whatwg/fetch] Proposal: Support GET bodies (#83)

> The Fetch Standard already requires that GET requests won't have a Content-Length header.

@annevk Could help me out with a link or citation for this?  One of my problems here just as a middle-man user trying to get software to play nice is I've got the httprb developer adamantly claiming he's not breaking any specs (just bending them IMO)  My understanding is the Fetch standard doesn't necessarily follow the HTTP RFCs-- is that correct?  A link to a spec that's actually being broken would be handy here.  Otherwise, it's just endless claiming that each side is correct.  

> they would take a patch, if you were to write one.

Yes, I'm aware, and you keep reading in that thread, you'll see the part where I explain why I'm not the person best-positioned to submit one.  This isn't just about "making code work", it's also about what's right and what's wrong and agreeing on what specs we're going to follow and what those specs do or do not say.  We know that https://datatracker.ietf.org/doc/html/rfc7230#section-3.3.2 does not expressly forbid an empty content-length header with a GET.  If there is another, more strict spec that Fetch is following, then at least identifying that will help.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/83#issuecomment-902903007