3 ms·
I feel one better fix is to just add a small random wait from the time </html> is served and the TCP socket is actually closed. I donnt think? this should impac
by justacomme555 8y ago
I feel one better fix is to just add a small random wait from the time </html> is served and the TCP socket is actually closed. I donnt think? this should impact loads of the page when it is rendered in an html context.
- yorwba 8y agoThe delay should not be simply random, it would need to be carefully chosen to make the load time distribution independent of the user loading the page. Otherwise an attacker could just average multiple requests to get rid of the randomness.
- justacomme555 8y agoYoure right... the delay would basically have to be chosen dynamically to enforce a universal page load time for all html documents on twitter.com Still feels nicer than forcing a roundtrip