Re: [whatwg/fetch] Reconsider treatment of non-GET for non-HTTP(S) schemes (#339)

I am not opposed to this change, I just do not understand the rationale and the problem it tries to solve.

For me, returning a network error seems simple, consistent and web-compatible. In any case, I would not special case blob scheme.

So, if most browsers agree with the standard, what is the value of changing the standard? Does it bring something new to the table?

Also, if HEAD is allowed for other URLs than HTTP(s), the semantics should be consistent for all URL schemes. That probably applies for other methods as well.



-- 
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/339#issuecomment-240242284