Re: Credentials and connection pools

On Mon, May 8, 2017 at 8:33 AM, Eric Rescorla <[email protected]> wrote:

> We cannot always retry. E.g., with fetch() using streams the user
> > agent cannot reproduce the body (by design, to use less memory;
> > therefore also fails on most redirects and HTTP authentication).
> >
>
> Hmm.... This seems like a separate topic, but as you describe it, this has
> the
> potential to interact very badly with TLS 1.3 0-RTT (and QUIC too) which
> both
> depend on the assumption that 0-RTT data can fail and have to be replayed
> semantically.



I don't think this is a fetch() level problem - those are both basically
transport issues with unacknowledged data and the transport is always going
to need a copy of that information to accommodate packet loss.. 0-rtt fail
is really just a twist on loss from a replay pov. Our definition of
transport has moved up a bit in the stack from socket buffers, but it
hasn't made it to fetch() yet :)