Mike West, July 2019 TL;DR: Let's break CSP in half and throw away some options while we're at it. Content Security Policy is a thing. We've been iterating on it for years and years now, and it shows. The backwards compatibility constraints are increasingly contorted, we've moved right past scope creep into scope kudzu, and the implementation status between browsers is inconsistent at best. I thin
This document defines a mechanism by which a web page can embed a nested browsing context if and only if it agrees to enforce a particular set of restrictions upon itself. This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in
This version: https://www.w3.org/TR/2024/WD-CSP3-20241014/ Latest published version: https://www.w3.org/TR/CSP3/ Editor's Draft: https://w3c.github.io/webappsec-csp/ Previous Versions: https://www.w3.org/TR/2024/WD-CSP3-20240909/ History: https://www.w3.org/standards/history/CSP3/ Feedback: public-webappsec@w3.org with subject line “[CSP3] … message topic …” (archives) Github Editors: Mike West (G
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く