Content-DPR header
{{securecontext_header}}{{Non-standard_header}}
The HTTP Content-DPR {{Glossary("response header")}}header is used to confirm the image device to pixel ratio (DPR) in requests where the screen {{HTTPHeader("DPR")}}DPR client hint was used to select an image resource.
[!NOTE]NOTE: TheContent-DPRheader was removed from the client hints specification in draft-ietf-httpbis-client-hints-07. The Responsive Image Client Hints specification proposes to replace this header by specifying intrinsic resolution/dimensions in EXIF metadata.
If the DPR client hint is used to select an image, the server must specify Content-DPR in the response.
If the value in Content-DPR is different from the {{HTTPHeader("DPR")}}DPR value in the request (i.e., image DPR is not the same as screen DPR), the client must use the Content-DPR for determining intrinsic image size and scaling the image.
If the Content-DPR header appears more than once in a message, the last occurrence is used.
| Header type |
|
|---|---|
| No | |
|
|
No |
Syntax
Content-DPR: <number>
Directives
<number>- : The image device pixel ratio, calculated according to the following formula: Content-DPR = Selected image resource size / (Width / DPR)
Examples
See the DPR header example.
Browser compatibility
{{Compat}}
See also
- Device and responsive image client hints
{{HTTPHeader("Sec-CH-Device-Memory")}}Memory{{HTTPHeader("Sec-CH-DPR")}}DPR{{HTTPHeader("Sec-CH-Viewport-Height")}}Height{{HTTPHeader("Sec-CH-Viewport-Width")}}Width
{{HTTPHeader("Accept-CH")}}CH- HTTP Caching: Vary and
{{HTTPHeader("Vary")}}Vary - Improving user privacy and developer experience with User-Agent Client Hints on developer.chrome.com (2020)