Skip to content

Range Requests

Gruxi supports HTTP range requests (as defined in RFC 9110), which allow clients to request specific byte ranges of files. This is particularly useful for resuming interrupted downloads, streaming media files, and optimizing bandwidth usage.

When a client makes a range request, it includes a Range header in the HTTP request specifying the desired byte range. Gruxi processes this request and responds with the appropriate portion of the file, along with a 206 Partial Content status code.

INFO

This feature is supported for static file serving in Gruxi. Ensure that your clients (e.g., web browsers, media players) support range requests to take advantage of this functionality. This is intentionally not supported for dynamic content generated by other processors, such as another web server or a scripting engine like PHP. They are best left to handle their own range requests as appropriate.

INFO

Gruxi announces support for range requests by including the Accept-Ranges: bytes header in responses for static files. This informs clients that they can make range requests for these resources.