HTTP Client Hints
draft-ietf-httpbis-client-hints-06
| Document | Type | Expired Internet-Draft (httpbis WG) | |
|---|---|---|---|
| Last updated | 2019-01-17 (latest revision 2018-07-16) | ||
| Replaces | draft-grigorik-http-client-hints | ||
| Stream | IETF | ||
| Intended RFC status | Experimental | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | In WG Last Call | |
| Document shepherd | Mark Nottingham | ||
| Shepherd write-up | Show (last changed 2016-11-21) | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | "Mark Nottingham" <mnot@mnot.net> | ||
https://www.ietf.org/archive/id/draft-ietf-httpbis-client-hints-06.txt
Abstract
An increasing diversity of Web-connected devices and software capabilities has created a need to deliver optimized content for each device. This specification defines an extensible and configurable 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 field allows user agents to indicate what formats they prefer, Client Hints allow user agents to indicate device and agent specific preferences.
Authors
Ilya Grigorik (ilya@igvita.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)