The Accept-Ranges
response HTTP header is a marker used by the server to advertise its support of partial requests. The value of this field indicates the unit that can be used to define a range.
In presence of an Accept-Ranges
header, the browser may try to resume an interrupted download, rather than to start it from the start again.
Header type | Response header |
---|---|
Forbidden header name | no |
Syntax
Accept-Ranges: <range-unit> Accept-Ranges: none
Directives
<range-unit>
- Defines the range unit the server supports. Though
bytes
is the only range unit formally defined by RFC 7233, additional range units may be registered in the HTTP Range Unit Registry. none
- No range unit is supported, this makes the header equivalent of its own absence and is therefore rarely used, though some browsers, like IE9, it is used to disable or remove the pause buttons in the download manager.
Examples
Accept-Ranges: bytes
Specifications
Specification | Title |
---|---|
RFC 7233, section 2.3: Accept-Ranges | Hypertext Transfer Protocol (HTTP/1.1): Range Requests |
Browser compatibility
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Accept-Ranges | Chrome Full support Yes | Edge Full support 12 | Firefox Full support Yes | IE Full support Yes | Opera Full support Yes | Safari Full support Yes | WebView Android Full support Yes | Chrome Android Full support Yes | Firefox Android Full support Yes | Opera Android Full support Yes | Safari iOS Full support Yes | Samsung Internet Android Full support Yes |
Legend
- Full support
- Full support