- From: Soni L. <fakedme+http@gmail.com>
- Date: Mon, 14 Aug 2023 13:32:12 -0300
- To: HTTP Working Group <ietf-http-wg@w3.org>
Let's say your server is sending a redirect to another page on the same server GET /whatever HTTP/1.1 ... 302 Found Location: /something Instead of waiting for the client to send the follow-up request, why not just send it straight away? 302 Found Location: /actually 200 OK ... This is different from server push in that it relies on making assumptions about how the client behaves, and it works with HTTP/1.1 too. The User-Agent header and some other fingerprinting techniques might be necessary for sending the right thing tho.
Received on Monday, 14 August 2023 16:32:28 UTC