Re: [whatwg/fetch] Provide ability to encode content from browser/runtime in fetch API. (#653) from sleevi on 2018-01-05 (public-webapps-github@w3.org from January 2018)

From: sleevi <notifications@github.com>
Date: Fri, 05 Jan 2018 15:45:48 +0000 (UTC)
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/653/355586595@github.com>

Correct, Chrome’s networking stack does not have methods or ability to encode uploads. Consumers of the network stack (in the non-Browser cases) are expected to do so. Servers - but also the things between servers (AV, caches, intermediaries) - are bad at this in the general case.

-- 
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/653#issuecomment-355586595

Received on Friday, 5 January 2018 15:46:17 UTC