Re: [whatwg/fetch] Define behavior in the presence of TLS Early Data (#888)

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

This is something that I think browsers should be able to determine on their own.  The spec can say "if the user agent sends the request in early data, ..." as necessary.

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

This is a good idea.  Adding `earlyData: bool` to the options struct is fine.

> Subresource integrity will turn it on.

See above regarding browser policy.  SRI is not a good signal here, but I don't think that we need to litigate the point.

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

The idea being that the browser retries?  That might not be feasible for requests with streamed bodies.  That would need some work.

-- 
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#issuecomment-479478888