Re: [w3ctag/design-reviews] Web Share Target API (#221)

@slightlyoff This raises a really good point. We've been thinking about `POST` as being the vehicle through which we deliver form data, so our plan was to only allow `GET` in the base version, but later add file sharing using `POST`. What I realised after reading your message is that `POST` isn't just a way of delivering large binary files; it also has different semantics (state mutating & non-repeatable).

I don't think we should **mandate** `POST` or make it the default, since many web share targets will not mutate state without further input from the user (e.g. https://twitter.com/intent/tweet?text=I%20use%20Web%20Share); refreshing these pages is fine and they are designed to be navigated with a `GET` request. The original point of using this URL-based design is to hook into those existing share mechanisms.

However, I now think we should support `POST` in the base standard for WST (so sites can reliably assume any user agent that supports WST also supports `"method": "POST"`). Even if you don't receive files, you can still use `"method": "POST"` if your site immediately mutates state without asking the user to confirm, and we should encourage sites to use the semantically appropriate method.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/221#issuecomment-400513601