HTTP Header Content Security Policy
draft-gondrom-websec-csp-header-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adam Barth , Tobias Gondrom | ||
| Last updated | 2012-09-06 (Latest revision 2012-03-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 communicate the Content Security Policy (CSP) as defined by the W3C, the web server needs to send a HTTP header to the browser (client) to inform it about the content security policies that SHALL be applied on the client. This draft outlines the header to communicate the CSP with its fields. The definition of the semantic of the directives will be done by the Web Application Security Working Group at the W3C.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)