Conversation

Notices

1. Benoit (benoit@toots.benpro.fr)'s status on Saturday, 18-Feb-2023 21:11:39 UTC Benoit

   TLS carries non-trivial overhead, especially for the initial request, due to the handshake. However, once established, HTTP/2 encapsulation can mitigate these costs.

   40ms here is quite high, when the static page also load at 40ms...

   Behind a WordPress or similar, these 40ms does not matter though. :reverse_grimacing:

   • Tagomago (tagomago@mastodon.social)'s status on Saturday, 18-Feb-2023 21:11:38 UTC Tagomago

     in reply to

     @benoit 40 ms is quite light even for a static page 🎈

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 18-Feb-2023 21:11:59 UTC Bernie

     in reply to

     • Tagomago

     @tagomago @benoit With HTTP/3 you'll get 0-RTT resume for GET requests and 1-RTT for POST, even when changing IP or after losing state on a NAT gateway.

   • Bernie (codewiz@mstdn.io)'s status on Saturday, 18-Feb-2023 21:12:24 UTC Bernie

     in reply to

     • Tagomago

     @tagomago @benoit With HTTP/3 you'll get 0-RTT resume for GET requests and 1-RTT for POST, even when changing IP or losing state on a NAT gateway.