HTTP Client Hints
This is an older version of an Internet-Draft that was ultimately published as RFC 8942.
Expired & archived
|Last updated||2016-05-27 (Latest revision 2015-11-24)|
|RFC stream||Internet Engineering Task Force (IETF)|
GENART Last Call review (of -13) by Christer Holmberg Ready w/issues
OPSDIR Last Call Review due 2020-05-08 Incomplete
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Associated WG milestone||
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
An increasing diversity of Web-connected devices and software capabilities has created a need to deliver optimized content for each device. This specification defines a set of HTTP request header fields, colloquially known as Client Hints, to address this. They are intended to be used as input to proactive content negotiation; just as the Accept header allows clients to indicate what formats they prefer, Client Hints allow clients to indicate a list of device and agent specific preferences.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)