[whatwg/fetch] Define behavior in the presence of TLS Early Data (#888) from Michael Howell on 2019-04-01 (public-webapps-github@w3.org from April 2019)

From: Michael Howell <notifications@github.com>
Date: Mon, 01 Apr 2019 16:58:04 +0000 (UTC)
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/888@github.com>

https://tools.ietf.org/html/rfc8470 specifies the 425 Response Code, but it is silent about how it should be exposed within the Web APIs.

I presume that it should be defined in such a way that:

* Page resources (destination != "") and navigation will be requested with early data as long as they don't have query parameters and use idempotent methods.

* Script requests are off-by-default, even if they're idempotent, but can explicitly turn it on.

* Subresource integrity will turn it on.

* 425 Too Early does not get reported to script. Like 304 Not Modified.

-- 
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/888

Received on Monday, 1 April 2019 16:58:26 UTC