W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Fetch API

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 4 Jun 2014 09:23:29 +0200
Message-ID: <CADnb78i8T4=MaR9pzcNBKEemeSW59gxii-V61-Zx3_p9XdcjaQ@mail.gmail.com>
To: Takeshi Yoshino <tyoshino@google.com>
Cc: public-script-coord <public-script-coord@w3.org>, Joshua Bell <jsbell@chromium.org>, Jungkee Song <jungkee.song@samsung.com>, Yehuda Katz <wycats@gmail.com>, Alex Russell <slightlyoff@google.com>, Jonas Sicking <jonas@sicking.cc>, Jake Archibald <jaffathecake@gmail.com>, Tobie Langel <tobie.langel@gmail.com>, WebApps WG <public-webapps@w3.org>
On Wed, Jun 4, 2014 at 8:13 AM, Takeshi Yoshino <tyoshino@google.com> wrote:
> On Mon, Jun 2, 2014 at 6:59 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> That's an internal algorithm never directly used. You can only get
>> there from http://fetch.spec.whatwg.org/#concept-fetch and that can
>> only be reached through an API such as fetch().
> Right. But preflight's client and context are not initialized before
> invoking HTTP fetch (http://fetch.spec.whatwg.org/#concept-http-fetch).
> client is referred in HTTP fetch.

Thanks! And my apologies for not getting that straight away.

> BTW, "handle a fetch" is a dead link.
> https://slightlyoff.github.io/ServiceWorker/spec/service_worker/handle-a-fetch


Received on Wednesday, 4 June 2014 07:24:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC