---
title: "Byte Range Request"
slug: "client-byte-range-request"
updated: 2025-05-21T10:08:34Z
published: 2025-05-21T10:08:34Z
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwilt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Client Byte Range Request

## Overview
The Client Byte Range Request rule allows for enabling or disabling client byte range requests for a particular host or path. Range request support is enabled by default. When Client Byte Range Request is disabled, the “Content-Range” header in client requests to the CDN is ignored and the complete file is delivered to the client. 

## Configure the Rule
Here, we'll describe how to configure the rule with the Delivery Service Management UI. 

API Users may choose to [build the site configuration offline](https://api-docs.qwilt.cqloud.com/docs/CDN%20APIs/Sites%20API/prepare-the-configuration-json).

**To configure a Byte Range Request rule:**
1. [Navigate to the Select Rule dialog](/v1/docs/add-a-rule).
2. In the Select Rule dialog, choose **Client Byte Range Request**. 
3. Toggle Client Byte Range Requests on or off.   

    ![clientByteRangeRequests2.png](https://cdn.document360.io/fa039225-513b-46a1-ba78-a57a1f1cb7c6/Images/Documentation/clientByteRangeRequests2.png){height="" width=""}

 
5. Choose **Add Rule**.



## SVTA Component: QW.HttpRangeRequests
When you save the configuration version, the **QW.HttpRangeRequests** component is added to the JSON configuration. This is a [private feature developed by Qwilt](https://api-docs.qwilt.cqloud.com/docs/CDN%20APIs/Sites%20API/Site%20Configuration%20JSON%20Format/prepare-the-configuration-json#qwilt-private-features). 

In this example, the QW.HttpRangeRequests SVTA component is configured to disable Client Byte Range Requests. 

```json
{
  "generic-metadata-type": "MI.PrivateFeature.Qwilt.QW.HttpRangeRequests",
  "generic-metadata-value": {
    "enable": false
  }
}
```