Conversation

Notices

1. Embed this notice
   :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 09-Sep-2024 15:48:03 JST :mima_rule: Mima-sama

   Idk why they had to kill off #http2 #serverpush. Yeah the way it's being used right now makes it useless, but it could've been used to shave off an RTT from HTTP 3XX responses... Imagine if a web server just immediately pushed the resource defined in the Location header after sending a 302 for example. It doesn't even have to be limited to HTTP/2 and newer, that can be backported to HTTP/1.1! :sagume_think:
   
   #HTTP

   • Embed this notice
     :blobcathug: (jain@blob.cat)'s status on Monday, 09-Sep-2024 15:48:01 JST :blobcathug:

     in reply to
     @mima that wont work, you would have to introduce a new header for setting the location client side too
   • Embed this notice
     :blobcathug: (jain@blob.cat)'s status on Monday, 09-Sep-2024 16:20:31 JST :blobcathug:

     in reply to
     @mima oh, sorry im wrong, its morning here and i didnt slept enough :ablobcatcoffee:
   • Embed this notice
     :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 09-Sep-2024 16:20:32 JST :mima_rule: Mima-sama

     in reply to

     • :blobcathug:

     @Jain@blob.cat And obviously client-side should change its own "address bar" to whatever the 200'd Location becomes, and all reloads should use it too

   • Embed this notice
     :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 09-Sep-2024 16:20:33 JST :mima_rule: Mima-sama

     in reply to

     • :blobcathug:

     @Jain@blob.cat wdym? I mean what I imagine the how of it being implemented is that both the client and server will have to use a new header to negotiate the capability for 3xx push (or "pipelined 3xx").. Kinda like this:
     GET /resource HTTP/1.1 Host: example.com Pipelined-3xx: HTTP/1.1 302 Found Pipelined-3xx: 1 Server: example Location: /actual-resource HTTP/1.1 200 OK Server: example Content-Type: text/html Content-Length: 792