As part of designing the fetch() API we try to offer web developers detailed control over the request and response. Even more so than XMLHttpRequest.
E.g. the idea is that in due course we offer response's body as a stream, on which content codings will not have been removed. Now for the request we have a ticket open, basically trying to figure out the minimal set of headers that would be acceptable to UAs: https://github.com/slightlyoff/ServiceWorker/issues/348 And then on top of that we would have to provide some convenient way of allowing cache headers, probably opting out of Referer (rather than opting in), ... Ideally we also standardize what headers we include for non-fetch() requests, such as those made by <img>, XMLHttpRequest, EventSource. And also whether a request payload ever has content codings applied. -- http://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
