2 ms·
Browsers are being cautious here initially, e.g. certainly the Chrome "intent to ship" post says they're doing ordinary 1RTT TLS 1.3 first Each TLS application
by tialaramex 8y ago
Browsers are being cautious here initially, e.g. certainly the Chrome "intent to ship" post says they're doing ordinary 1RTT TLS 1.3 first
Each TLS application (e.g. HTTP) is expected to write up a "profile" if it wants 0RTT which explains how to do it safely. The one for HTTP is currently in draft. The most obvious thing is: truly idempotent operations are safe. GET /favicon.ico looks pretty safe for example. If you log it, and bad guys can cause you to log it more than once, well, OK, but so what?
On the other hand GET /database/delete/yes-really was already a bad idea before 0RTT and there's an arguement that we should not help people shoot themselves in the foot.
Since both sides need to agree to do it, if it turns out that the nice speed up isn't worth the endless feet blown off by it we can expect web browsers to just switch it off.