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

IETF · RFC · RFC7694

RFC7694 · Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding

Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding

In HTTP, content codings allow for payload encodings such as for compression or integrity checks. In particular, the "gzip" content coding is widely used for payload data sent in response messages. Content codings can be used in request messages as well; however, discoverability is not on par with response messages. This document extends the HTTP "Accept-Encoding" header field for use in responses, to indicate the content codings that are supported in requests.

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

In HTTP, content codings allow for payload encodings such as for compression or integrity checks. In particular, the "gzip" content coding is widely used for payload data sent in response messages. Content codings can be used in request messages as well; however, discoverability is not on par with response messages. This document extends the HTTP "Accept-Encoding" header field for use in responses, to indicate the content codings that are supported in requests.

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

obsoleted_by: RFC9110

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

Полные импортированные сведения карточки
{
  "id": "RFC7694",
  "number": 7694,
  "title_en": "Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding",
  "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": "In HTTP, content codings allow for payload encodings such as for compression or integrity checks. In particular, the \"gzip\" content coding is widely used for payload data sent in response messages. Content codings can be used in request messages as well; however, discoverability is not on par with response messages. This document extends the HTTP \"Accept-Encoding\" header field for use in responses, to indicate the content codings that are supported in requests.",
  "authors": [
    "J. Reschke"
  ],
  "organizations": [],
  "publication_date": "2015-11-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "httpbis",
  "source_draft": "draft-ietf-httpbis-cice-03",
  "page_count": 7,
  "doi": "10.17487/RFC7694",
  "keywords": [
    "HTTP",
    "content-encoding"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC9110"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7694/",
    "html": "https://www.rfc-editor.org/rfc/rfc7694.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7694.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7694/"
  }
}