News for hackers. Stuff that matters.
Re:HTTP 103 – An HTTP Status Code for Indicating Hints by alexbecker on Monday October 30, 2017 @09:00PM (#15590370)
As I understand it, the status code would improve performance in situations like the following:

1. Client requests X.html (which requires Y.css and Z.js) from Proxy.

2. Proxy forwards client's X.html request to Server.

3. [Server takes a long time to respond]

4. Server sends a 200 response to Proxy with X.html.

5. Proxy, per some configuration, adds Preload headers to this response indicating that Y.css and Z.js should be immediately loaded once this response is received, and sends it to Client.

6. Client requests Y.css and Z.js.

With the 103 status code, this would look like:

1. Client requests X.html (which requires Y.css and Z.js) from Proxy.

2. Proxy forwards client's X.html request to server and, per some configuration, immediately sends a 103 response with Preload headers for Y.css and Z.js to Client.

3. [Server takes a long time to respond]

4. In parallel, Client requests Y.css and Z.js.

5. Server sends a 200 response to Proxy with X.html.

6. Proxy sends this response to Client.

Note that since Y.css and Z.js are requested sooner, the final load time should be less.

Re:HTTP 103 – An HTTP Status Code for Indicating Hints by stock_toaster on Monday October 30, 2017 @09:46PM (#15590566)
The proxy could also read preload headers from the Server, and start preemptively fetching Y.css and Z.js from the Server at the same time (step 2) it forwards the preload headers back to Client.