Ranged Web Requests (demo) by Anon

We have become accustomed to browsers being able to resume downloads if they are interrupted. However, for web pages and the resources they load - images, stylesheets, scripts, etc., - this capability is not available. This extension demonstrates that solving this problem is indeed possible.

What is implemented in this extension: If the server supports the Range header and doesn't use compression, the GET request is split into several parts, with each subsequent part having a size that increases or decreases depending on the transfer speed and errors encountered with the previous ones.

Features that are not yet implemented but could be added: more complex cases where the server uses compression or Transfer-Encoding: chunked.

What cannot be implemented through an extension and requires browser modifications itself: replacing the HTTP status code from 206 with the actual request status. In responses to Range headers, servers send an HTTP Response code of 206, which can be an issue when certain web applications explicitly expect a different response code (e.g., 200).

The purpose of this extension is threefold: to showcase that this problem exists, demonstrate its possible solution, and highlight the need for such a fix. It may potentially expedite the inclusion of similar features in browsers themselves or serve as a temporary workaround for individuals seeking a solution.