0-RTT may class as "Yes" rather than "warn". Fastly say:
Fastly currently only supports 0-RTT between Fastly and requesting clients. We do not support 0-RTT between Fastly and your origin servers.
By default, Fastly only answers idempotent requests (GET and HEAD requests without query parameters) over 0-RTT. This helps protect customer applications from replay attacks.
Requests issued with 0-RTT will include an Early-Data:1 header per RFC 8470. This attribute can be queried and logged via VCL using req.http.early-data.
Press release and video: https://www.fastly.com/blog/tls13-available
0-RTT may class as "Yes" rather than "warn". Fastly say:
Closes #202