Skip to content

Commit 04a5795

Browse files
authored
Update corp.md
Implementing agreed-on changes.
1 parent 5ae9f6d commit 04a5795

1 file changed

Lines changed: 3 additions & 6 deletions

File tree

  • content/docs/defenses/opt-in

content/docs/defenses/opt-in/corp.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,10 @@ Cross-Origin Resource Policy (CORP) is a web platform security feature that allo
1212

1313
If an application sets a certain resource CORP header as 'same-site' or 'same-origin', an attacker is incapable of reading that resource. This is a very strong and highly encouraged protection.
1414

15-
{{< hint warning >}}
16-
CORP does not protect against navigational requests. This means that in browsers that do not support out-of-process iframes, a CORP-protected resource may still end up in another origin's process if [framing protections]({{< ref "../opt-in/xfo.md" >}}) are not used.
17-
{{< /hint >}}
15+
When using CORP, be aware of the following facts:
1816

19-
{{< hint warning >}}
20-
This mechanism introduces [a new XS-Leak]({{< ref "../../attacks/browser-features/corp.md" >}}), which allows attackers to detect whether CORP was enforced in a certain request.
21-
{{< /hint >}}
17+
* CORP does not protect against navigational requests. This means that in browsers that do not support out-of-process iframes, a CORP-protected resource may still end up in another origin's process if [framing protections]({{< ref "../opt-in/xfo.md" >}}) are not used.
18+
* The use of CORP introduces [a new XS-Leak]({{< ref "../../attacks/browser-features/corp.md" >}}), which allows attackers to detect whether CORP was enforced in a certain request.
2219

2320
## References
2421

0 commit comments

Comments
 (0)