HTTP Strict Transport Security (HSTS)
draft-hodges-strict-transport-sec-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Jeff Hodges , Collin Jackson , Adam Barth | ||
Last updated | 2011-08-26 (Latest revision 2010-07-12) | ||
Replaced by | draft-ietf-websec-strict-transport-sec | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-websec-strict-transport-sec | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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, e.g. user agent configuration.
Authors
Jeff Hodges
Collin Jackson
Adam Barth
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)