public-webappsec@w3.org from June 2015 by subject

[Bug 28861] New: Section 6.2 Preflight Request, step 10, second note: "Access-Control-Allow-Headers" instead of "Access-Control-Request-Headers"

[credential management] Cross-origin credentials

[credential management] Cross-origin credentials (was: Identity Credentials API Extension)

[credential management] Identity Credentials API Extension

[credential-management] initial feedback

[REFERRER] updating referrer policy and request caching

[upgrade-insecure-requests] Strict-Transport-Security only for HTML document or any type files?

[webappsec] CfC: Proposed non-normative updates to CORS

[webappsec] Reminder: Berlin F2F July 13-14

[webappsec] Teleconference Agenda 15-June-2015 12:00 PDT

[webappsec] Teleconference Agenda 29-Jun

[webappsec] TPAC registration is open!

Berlin F2F Participation

Call for Exclusions: Entry Point Regulation

CfC: Mixed Content to PR; deadline July 6th.

Chrome. Re: Post-Zakim calls? (Re: [webappsec] Teleconference Agenda 29-Jun)

CORS performance proposal

CSP unsafe-inline DOM access

Every example fails

F2F Meeting?

Is secure context enough of a guarantee?

Post-Zakim calls? (Re: [webappsec] Teleconference Agenda 29-Jun)

Proposal: a "clear site data" API.

some brief comments on mixedcontent

SRI: Behavior when a developer fails to specify CORS

SRI: Shipped on tip-of-tree Chromium

UPGRADE: 'HTTPS' header causing compatibility issues.

Where to file RFC 6455 bugs? [Was: Re: CfC: Mixed Content to PR; deadline July 6th.]

Last message date: Tuesday, 30 June 2015 23:56:59 UTC