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

> The server cannot assume that a client is able to retry a request unless the request is received in early data or the Early-Data header field is set to "1".

And elsewhere there is text that this header is not to be set by user agents. (and I'm not sure that setting it in `fetch()` would really test anything in the user agent).

I think that means that unless we can test TLS early data on WPT (do you know?) Firefox's behavior of always passing on the 425 makes the most sense.

And yeah, I'm okay with your tests being sufficient here and leaving further cleanup for later. (I'll repeat my wish for IETF taking more ownership in end-to-end integration of new features.)

-- 
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-796557213