CSP: 'no-external-navigation'?
[MIX]: Can we distinguish between images loader via `<picture>`/`srcset` and `<img>`?
- Re: [MIX]: Can we distinguish between images loader via `<picture>`/`srcset` and `<img>`?
Isolated Web Components for a more secure web
Re: CSP wildcard host matching
[MIX] blob URLs
Proposal: Prefer secure origins for powerful new web platform features
- Re: Proposal: Prefer secure origins for powerful new web platform features
- Re: Proposal: Prefer secure origins for powerful new web platform features
- Re: [blink-dev] Proposal: Prefer secure origins for powerful new web platform features
- Re: Proposal: Prefer secure origins for powerful new web platform features
[CSP] Additional report field: report-only: "true|false"
CfC to publish FPWD of Mixed Content.
Naming things: CSP 1.1 -> CSP level 2?
Reducing reporting noise
PFWG comments on User Interface Security Directives for Content Security Policy
webappsec-ISSUE-62: is reflected-xss at risk?
ISSUE-61: Should we mark referrer and reflected-xss as at risk in csp 1.1 lcwd?
[webappsec] WebAppSec WG Teleconference Agenda 18-June-2014
Call for Exclusions (Update): Subresource Integrity
[integrity] The noncanonical-src attribute
CSP: Problems with referrer and reflected-xss
Standardize referrer policy
[Bug 26061] New: Improve consistency with CSP 1.1 w.r.t. add-on/extension semantics.
CfC to publish a LCWD of CSP 1.1
- Re: CfC to publish a LCWD of CSP 1.1
- Re: CfC to publish a LCWD of CSP 1.1
- Re: CfC to publish a LCWD of CSP 1.1
Re: [MIX]: "Assumed"/"Proven" Terminology.
Header Policy Vs. Meta tag policy
Header Policy Vs. Meta tag policy
- Re: Header Policy Vs. Meta tag policy
Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
[MIX]: "Assumed"/"Proven" Terminology. (Re: [MIX]: Expand scope beyond TLS/non-TLS)
[MIX] localhost should not be trusted
CSP: Block redirects by default?
[webappsec] Help build the CSP test suite at Test the Web Forward Portland, August 3
- Re: [webappsec] Help build the CSP test suite at Test the Web Forward Portland, August 3
[CSP] enforcement on non text-html resources
[MIX]: Move specifics to a non-normative section/document? (Re: "Mixed Content" draft up for review.)
- Re: [MIX]: Move specifics to a non-normative section/document? (Re: "Mixed Content" draft up for review.)
[MIX]: Expand scope beyond TLS/non-TLS (Re: "Mixed Content" draft up for review.)
Agenda, 5 June 2014 SVG WG / WebAppSec WG telcon
[MIX] Comments on draft Mixed Content spec
Re: CSP, Fetch, and frame-ancestors
Discuss SVG and CSP for the June 5 SVG teleconference
[webappsec] Teleconference Agenda: 04-Jun-2014
[MIX]: 'allow-from' header? (Re: "Mixed Content" draft up for review.)
[MIX] Checking parent/top (Re: "Mixed Content" draft up for review.)
Re: "Mixed Content" draft up for review - HSTS interworking
Re: "Mixed Content" draft up for review - HSTS primary purpose
Re: "Mixed Content" draft up for review.
- Re: "Mixed Content" draft up for review.
- Re: "Mixed Content" draft up for review.
- Re: "Mixed Content" draft up for review.
- Re: "Mixed Content" draft up for review.
- Re: "Mixed Content" draft up for review.