HTTP/2 Re-requests: Improving Performance with Multiple Concurrent Requests

Re-request is a feature in HTTP/2 that allows a client to send a new request to the server before receiving the complete response for the previous request. This can be useful in situations where the client needs to send multiple requests to the server quickly, such as when loading a web page with multiple resources.

In HTTP/1.1, clients had to wait for the entire response to be received before sending another request. However, with HTTP/2, clients can send a new request before the previous response is complete, allowing for more efficient use of network resources and improved performance.

Re-request is also known as "zero-copy" or "in-flight" requests, because the client does not need to receive the entire response for the previous request before sending the next one. Instead, the client can send a new request while the previous response is still being transmitted, allowing for more concurrent requests and faster overall performance.

I like this

I dislike this

Report a content error

Share

Report a content error

Thank you! Your form was successfully submitted.

We apologize! Your form could not be submitted. Please try again later.

Submit reports

Share

• 
• 
• 
• 
• 
• 
• 
• 
•