HTTP Client Hints
draft-grigorik-http-client-hints-03
| Document | Type | Replaced Internet-Draft (candidate for httpbis WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2015-08-24) | ||
| Replaced by | draft-ietf-httpbis-client-hints | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-client-hints | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-grigorik-http-client-hints-03.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 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.
Authors
Ilya Grigorik (ilya@igvita.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)