Re: HTTP profile for TLS 1.3 0-RTT early data?

On Wed, May 10, 2017 at 8:23 PM, Mark Nottingham <mnot@mnot.net> wrote:

> > 4) Perhaps a general HTTP request header for indicating that requests
> were received via 0RTT early data (such as Cloudflare's "Cf-0rtt-Unique"
> header).  This would be useful for both load balancers communicating to
> application servers, as well as for CDNs communicating to origin servers.
> This would presumably interact with #2 in cases where the appserver or
> origin wanted to force a client to retry via 1-RTT.
>
> Seems reasonable. Then you could Vary on it. *evil grin*
>


this has some terrible hpack interactions if replay isn't really replay of
the same byte stream.