HTTP Header Frame Options
draft-gondrom-frame-options-02
| Document | Type |
Replaced Internet-Draft
(websec WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Ross, Tobias Gondrom | ||
| Last updated | 2012-07-10 (Latest revision 2012-03-05) | ||
| Replaced by | draft-ietf-websec-frame-options | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Alexey Melnikov | ||
| IESG | IESG state | Replaced by draft-ietf-websec-frame-options | |
| Consensus boilerplate | Unknown | ||
| 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
To improve the protection of web applications against Cross Site Request Forgery (CSRF) and Clickjacking this standards defines a http response header that declares a policy communicated from a host to the client browser whether the transmitted content MUST NOT be displayed in frames of other pages from different origins or a list of trusted origins which are allowed to frame the content.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)