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

IETF · RFC · RFC3230

RFC3230 · Instance Digests in HTTP

Instance Digests in HTTP

HTTP/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body. However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding). Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances. Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest. This document proposes HTTP extensions that solve these problems. [STANDARDS-TRACK]

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

HTTP/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body. However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding). Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances. Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest. This document proposes HTTP extensions that solve these problems. [STANDARDS-TRACK]

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

obsoleted_by: RFC9530

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

Полные импортированные сведения карточки
{
  "id": "RFC3230",
  "number": 3230,
  "title_en": "Instance Digests in HTTP",
  "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/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body. However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding). Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances. Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest. This document proposes HTTP extensions that solve these problems. [STANDARDS-TRACK]",
  "authors": [
    "J. Mogul",
    "A. Van Hoff"
  ],
  "organizations": [],
  "publication_date": "2002-01-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "Legacy",
  "stream_ru": "Исторический поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "draft-mogul-http-digest-05",
  "page_count": 13,
  "doi": "10.17487/RFC3230",
  "keywords": [
    "HTTP",
    "hypertext transfer protocol"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC9530"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3230/",
    "html": "https://www.rfc-editor.org/rfc/rfc3230.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3230.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3230/"
  }
}