Skip to content

Commit b05cfac

Browse files
authored
Remove RECOMMENDATION to not send multiple CSP headers (#622)
1 parent 66216b4 commit b05cfac

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

index.bs

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -908,10 +908,6 @@ spec: WebRTC; urlPrefix: https://www.w3.org/TR/webrtc/
908908
A server MAY send different `Content-Security-Policy` header field
909909
values with different <a>representations</a> of the same resource.
910910

911-
A server SHOULD NOT send more than one HTTP response header field named
912-
"`Content-Security-Policy`" with a given <a>resource
913-
representation</a>.
914-
915911
When the user agent receives a `Content-Security-Policy` header field, it
916912
MUST <a abstract-op lt="parse a serialized CSP">parse</a> and <a>enforce</a> each
917913
<a>serialized CSP</a> it contains as described in [[#fetch-integration]],
@@ -949,10 +945,6 @@ spec: WebRTC; urlPrefix: https://www.w3.org/TR/webrtc/
949945
header field values with different <a>representations</a> of the same
950946
resource.
951947

952-
A server SHOULD NOT send more than one HTTP response header field named
953-
"`Content-Security-Policy-Report-Only`" with a given <a>resource
954-
representation</a>.
955-
956948
When the user agent receives a `Content-Security-Policy-Report-Only` header
957949
field, it MUST <a abstract-op lt="parse a serialized CSP">parse</a> and <a>monitor</a>
958950
each <a>serialized CSP</a> it contains as described in

0 commit comments

Comments
 (0)