⌕ Поиск по атласу

IETF · RFC · RFC8942

RFC8942 · HTTP Client Hints

HTTP Client Hints

HTTP defines proactive content negotiation to allow servers to select the appropriate response for a given request, based upon the user agent's characteristics, as expressed in request headers. In practice, user agents are often unwilling to send those request headers, because it is not clear whether they will be used, and sending them impacts both performance and privacy. This document defines an Accept-CH response header that servers can use to advertise their use of request headers for proactive content negotiation, along with a set of guidelines for the creation of such headers, colloquially known as "Client Hints."

Официальная английская аннотация

HTTP defines proactive content negotiation to allow servers to select the appropriate response for a given request, based upon the user agent's characteristics, as expressed in request headers. In practice, user agents are often unwilling to send those request headers, because it is not clear whether they will be used, and sending them impacts both performance and privacy. This document defines an Accept-CH response header that servers can use to advertise their use of request headers for proactive content negotiation, along with a set of guidelines for the creation of such headers, colloquially known as "Client Hints."

Связи документа

Официальный источник · 2021-02-01

Полные импортированные сведения карточки
{
  "id": "RFC8942",
  "number": 8942,
  "title_en": "HTTP Client Hints",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "HTTP defines proactive content negotiation to allow servers to select the appropriate response for a given request, based upon the user agent's characteristics, as expressed in request headers. In practice, user agents are often unwilling to send those request headers, because it is not clear whether they will be used, and sending them impacts both performance and privacy. This document defines an Accept-CH response header that servers can use to advertise their use of request headers for proactive content negotiation, along with a set of guidelines for the creation of such headers, colloquially known as \"Client Hints.\"",
  "authors": [
    "I. Grigorik",
    "Y. Weiss"
  ],
  "organizations": [],
  "publication_date": "2021-02-01",
  "current_status": "EXPERIMENTAL",
  "current_status_ru": "Экспериментальный",
  "publication_status": "EXPERIMENTAL",
  "publication_status_ru": "Экспериментальный",
  "lifecycle": "experimental",
  "lifecycle_ru": "Экспериментальный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "httpbis",
  "source_draft": "draft-ietf-httpbis-client-hints-15",
  "page_count": 10,
  "doi": "10.17487/RFC8942",
  "keywords": [
    "Content Negotiation"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8942/",
    "html": "https://www.rfc-editor.org/rfc/rfc8942.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8942.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8942/"
  }
}