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

IETF · RFC · RFC6797

RFC6797 · HTTP Strict Transport Security (HSTS)

HTTP Strict Transport Security (HSTS)

This specification defines a mechanism enabling web sites to declare themselves accessible only via secure connections and/or for users to be able to direct their user agent(s) to interact with given sites only over secure connections. This overall policy is referred to as HTTP Strict Transport Security (HSTS). The policy is declared by web sites via the Strict-Transport-Security HTTP response header field and/or by other means, such as user agent configuration, for example. [STANDARDS-TRACK]

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

This specification defines a mechanism enabling web sites to declare themselves accessible only via secure connections and/or for users to be able to direct their user agent(s) to interact with given sites only over secure connections. This overall policy is referred to as HTTP Strict Transport Security (HSTS). The policy is declared by web sites via the Strict-Transport-Security HTTP response header field and/or by other means, such as user agent configuration, for example. [STANDARDS-TRACK]

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

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

Полные импортированные сведения карточки
{
  "id": "RFC6797",
  "number": 6797,
  "title_en": "HTTP Strict Transport Security (HSTS)",
  "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": "This specification defines a mechanism enabling web sites to declare themselves accessible only via secure connections and/or for users to be able to direct their user agent(s) to interact with given sites only over secure connections. This overall policy is referred to as HTTP Strict Transport Security (HSTS). The policy is declared by web sites via the Strict-Transport-Security HTTP response header field and/or by other means, such as user agent configuration, for example. [STANDARDS-TRACK]",
  "authors": [
    "J. Hodges",
    "C. Jackson",
    "A. Barth"
  ],
  "organizations": [],
  "publication_date": "2012-11-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "app",
  "area_ru": "app",
  "working_group": "websec",
  "source_draft": "draft-ietf-websec-strict-transport-sec-14",
  "page_count": 46,
  "doi": "10.17487/RFC6797",
  "keywords": [
    "HTTPS",
    "TLS",
    "SSL",
    "ForceHTTPS",
    "man-in-the-middle",
    "MITM",
    "certificate error",
    "certificate verification",
    "security policy",
    "secure transport",
    "IDNA-Canonicalization"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6797/",
    "html": "https://www.rfc-editor.org/rfc/rfc6797.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6797.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6797/"
  }
}