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

Let's recap.

1. All browsers allow any method for about URLs.
2. Data URLs are inconsistent. Firefox allows other methods, Chrome does not, but you mentioned WebKit does. http://w3c-test.org/fetch/api/basic/scheme-data.html does not work in Safari Technology Preview for me.
3. Blob URLs seem consistent in rejecting non-GET: http://w3c-test.org/fetch/api/basic/scheme-blob.html.

What @sicking wants is consistency across schemes. I don't care too strongly about that, but it's arguably better that if we have no argument to restrict methods we should allow all of them. And HEAD is the only one with the special semantics, but its special semantics are handled in "main fetch" already for all responses.

-- 
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-240328452