public-webappsec@w3.org from December 2014 by date

Tuesday, 30 December 2014

• Re: [SRI] unsupported hashes and invalid metadata Francois Marier
• Re: Proposal: Marking HTTP As Non-Secure Eric Mill

Sunday, 28 December 2014

• [REFERRER] Combination of referrer directive values sourcekick

Tuesday, 30 December 2014

• Re: [CSP] different perspective on Report-Only Brad Hill
• Re: [CSP3] Allow plugin-types "none" Brad Hill
• webappsec-ISSUE-74 (plugin-types 'none'): allow explicitly setting the 'none' keyword source for plugin-type directive [CSP Level 3] Web Application Security Working Group Issue Tracker
• Re: [CSP3] Allow paths without a domain Brad Hill
• webappsec-ISSUE-73 (CSP path matching): Consider allowing relative paths (to 'self') in source productions [CSP Level 3] Web Application Security Working Group Issue Tracker
• [CSP3] Allow plugin-types "none" Craig Francis
• [CSP3] Allow paths without a domain Craig Francis
• Re: [SRI] providing good defaults when the expected content type is missing? Brad Hill
• Re: [SRI] unsupported hashes and invalid metadata Brad Hill
• AW: [CSP] different perspective on Report-Only Ludwig, Sven
• Re: [CSP] different perspective on Report-Only Mike West
• Re: Proposal: Marking HTTP As Non-Secure Jim Manico
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Jim Manico
• [SRI] providing good defaults when the expected content type is missing? Francois Marier
• [CSP] How to interpret 'self' in a sandboxed iframe Joel Weinberger
• Re: [SRI] unsupported hashes and invalid metadata Chris Palmer

Monday, 29 December 2014

• Re: [SRI] unsupported hashes and invalid metadata Francois Marier
• AW: [CSP] different perspective on Report-Only Ludwig, Sven
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Reminder: today's webappsec teleconference CANCELED Brad Hill
• Re: [CSP] different perspective on Report-Only Mike West

Sunday, 28 December 2014

• Re: Public Key Pinning (was Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure) Ryan Sleevi
• Re: Public Key Pinning (was Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure) Jeffrey Walton
• Re: Public Key Pinning (was Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure) Chris Palmer
• Why not DNS records Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Austin William Wright
• Re: [SRI] unsupported hashes and invalid metadata Devdatta Akhawe
• Re: [CSP] different perspective on Report-Only Martin Thomson

Saturday, 27 December 2014

• Re: Public Key Pinning (was Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure) Jeffrey Walton
• Re: Public Key Pinning (was Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure) Ryan Sleevi
• Public Key Pinning (was Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure) Jeffrey Walton

Friday, 26 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Jiri Danek

Saturday, 27 December 2014

• [CSP] different perspective on Report-Only Ludwig, Sven
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Craig Francis
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Austin William Wright
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Austin William Wright
• Re: Proposal: Marking HTTP As Non-Secure Brian Smith
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Jeffrey Walton
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Austin William Wright

Friday, 26 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Jim Manico
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Craig Francis
• Re: [SRI] unsupported hashes and invalid metadata Mike West
• Re: [REFERRER] feedback - Editorial comment: s/referer/Referer/g Mike West
• [REFERRER] feedback - Editorial comment: s/referer/Referer/g David Booth

Wednesday, 24 December 2014

• [SRI] unsupported hashes and invalid metadata Francois Marier
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Alex Russell
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Jeffrey Walton
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Alex Russell
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Alex Russell
• Re: Proposal: Marking HTTP As Non-Secure Austin William Wright

Tuesday, 23 December 2014

• Fwd: Proposed W3C Charter: Web Application Security Working Group (Call for Review) Wendy Seltzer

Wednesday, 17 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure softwaredevjirka@gmail.com

Saturday, 20 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Jiri Danek

Monday, 22 December 2014

• Re: Proposal: Marking HTTP As Non-Secure ianG
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure ianG
• Re: Proposal: Marking HTTP As Non-Secure ianG

Saturday, 20 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Craig Francis

Monday, 22 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Donald Stufft
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Sigbjørn Vik
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Anne van Kesteren
• Re: Proposal: Marking HTTP As Non-Secure Gervase Markham
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Gervase Markham

Sunday, 21 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Henri Sivonen
• Re: [webappsec] Next WebAppSec teleconference Mike West

Saturday, 20 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Adrienne Porter Felt
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Donald Stufft
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez

Friday, 19 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Tyler Larson
• [webappsec] Next WebAppSec teleconference Brad Hill
• Re: Proposal: Marking HTTP As Non-Secure Monica Chew
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Donald Stufft
• RE: [blink-dev] Proposal: Marking HTTP As Non-Secure Domenic Denicola
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Patrick Kolodziejczyk
• Re: Proposal: Marking HTTP As Non-Secure Gervase Markham
• Re: Proposal: Marking HTTP As Non-Secure Monica Chew

Thursday, 18 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Monica Chew
• Re: Proposal: Marking HTTP As Non-Secure Monica Chew
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Monica Chew
• Re: Proposal: Marking HTTP As Non-Secure Monica Chew
• Re: Proposal: Marking HTTP As Non-Secure jstriegel@google.com

Friday, 19 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Chris Bentzel
• Re: Marking HTTP As Non-Secure Igor Bukanov
• Re: Marking HTTP As Non-Secure Eduardo' Vela\
• Re: Marking HTTP As Non-Secure Michal Zalewski
• RE: Marking HTTP As Non-Secure Patrick Kolodziejczyk
• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Anne van Kesteren
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Matthew Dempsky
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Donald Stufft
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Donald Stufft
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Matthew Dempsky

Thursday, 18 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Daniel Kahn Gillmor
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Daniel Kahn Gillmor
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Michael Martinez
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Jeffrey Walton
• Re: Proposal: Marking HTTP As Non-Secure Daniel Kahn Gillmor
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Peter Kasting
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Peter Kasting
• Re: Proposal: Marking HTTP As Non-Secure Adrienne Porter Felt
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Jeffrey Walton
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Peter Kasting
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Gervase Markham
• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Brad Hill
• Re: Marking HTTP As Non-Secure Michael Martinez
• Re: Marking HTTP As Non-Secure Michael Martinez
• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Michael Cooper
• Re: Marking HTTP As Non-Secure Daniel Kahn Gillmor
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Daniel Kahn Gillmor
• Re: Marking HTTP As Non-Secure Eduardo' Vela\
• Re: Marking HTTP As Non-Secure Daniel Kahn Gillmor
• Re: Marking HTTP As Non-Secure Mathias Bynens

Wednesday, 17 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Stephen Gallagher
• Marking HTTP As Non-Secure Patrick Kolodziejczyk
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Matthew Dempsky

Thursday, 18 December 2014

• Re: Proposal: Marking HTTP As Non-Secure michaelhorowitz@gmail.com

Wednesday, 17 December 2014

• Re: Proposal: Marking HTTP As Non-Secure gshollingsworth@gmail.com
• Re: Proposal: Marking HTTP As Non-Secure tylerl@google.com

Thursday, 18 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure chaals@yandex-team.ru

Wednesday, 17 December 2014

• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Brad Hill
• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Michael Cooper
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure chaals@yandex-team.ru
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Sigbjørn Vik
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Anne van Kesteren
• Re: Proposal: Marking HTTP As Non-Secure Sigbjørn Vik
• Re: Proposal: Marking HTTP As Non-Secure Adrienne Porter Felt
• Re: Proposal: Marking HTTP As Non-Secure Håvard Molland
• Re: Proposal: Marking HTTP As Non-Secure Sigbjørn Vik
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West

Tuesday, 16 December 2014

• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Andy Wingo

Monday, 15 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Adrienne Porter Felt

Tuesday, 16 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Donald Stufft
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brian Smith
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brad Hill
• Security UI Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure chaals@yandex-team.ru
• Re: Proposal: Marking HTTP As Non-Secure Sigbjørn Vik
• Re: MIX: Exiting last call? Anne van Kesteren
• Re: Service Workers and MIX (was Re: MIX: Exiting last call?) Anne van Kesteren
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Brad Hill
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brian Smith
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Mike West
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: [blink-dev] Re: Proposal: Marking HTTP As Non-Secure Peter Kasting
• Re: Proposal: Marking HTTP As Non-Secure Christian Heutger
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Christian Heutger
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi

Monday, 15 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Alex Gaynor
• postMessage, workers and sandboxing Brad Hill
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brad Hill
• webappsec-ACTION-208: Take charter to w3m for review Web Application Security Working Group Issue Tracker
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brad Hill
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brad Hill
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brad Hill
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Re: MIX: Exiting last call? Daniel Veditz
• Re: Strict mixed content checking (was Re: MIX: Exiting last call?) Brad Hill
• Re: Proposal: Marking HTTP As Non-Secure Daniel Veditz
• Strict mixed content checking (was Re: MIX: Exiting last call?) Mike West
• Service Workers and MIX (was Re: MIX: Exiting last call?) Mike West
• Re: MIX: Exiting last call? Mike West
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Ryan Sleevi
• Re: Proposal: Marking HTTP As Non-Secure Michal Zalewski
• Re: Proposal: Marking HTTP As Non-Secure Jeffrey Walton
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure chaals@yandex-team.ru

Saturday, 13 December 2014

• Re: [blink-dev] Proposal: Marking HTTP As Non-Secure Mathias Bynens
• Re: Proposal: Marking HTTP As Non-Secure Christian Heutger

Sunday, 14 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Christian Heutger

Saturday, 13 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov

Sunday, 14 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Igor Bukanov
• Re: Proposal: Marking HTTP As Non-Secure Peter Bowen

Saturday, 13 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Alex Gaynor

Sunday, 14 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Alex Gaynor

Monday, 15 December 2014

• Re: [webappsec] Teleconference Agenda, Monday 14-Dec-2014 Brian Smith
• Re: MIX: Exiting last call? Brian Smith

Sunday, 14 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Michal Zalewski
• Re: Proposal: Marking HTTP As Non-Secure Michal Zalewski
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: [webappsec] Teleconference Agenda, Monday 14-Dec-2014 Frederik Braun

Saturday, 13 December 2014

• Re: Proposal: Marking HTTP As Non-Secure Chris Palmer
• Re: Proposal: Marking HTTP As Non-Secure Eduardo Robles Elvira
• Proposal: Marking HTTP As Non-Secure Chris Palmer

Friday, 12 December 2014

• Re: [webappsec] Teleconference Agenda, Monday 14-Dec-2014 Brad Hill
• Re: [webappsec] Teleconference Agenda, Monday 14-Dec-2014 Giorgio Maone
• [webappsec] Teleconference Agenda, Monday 14-Dec-2014 Brad Hill
• Re: [CSP3] Please define the encoding used for violation reports Brad Hill
• RE: [REFERRER][CSP] Improving the Web Platform's Referrer Policy Mike O'Neill
• MIX: Exiting last call? Mike West

Thursday, 11 December 2014

• Re: Comments on Mixed Content Anne van Kesteren
• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Mike West
• Re: Comments on Mixed Content Mike West
• Re: [SRI] Towards v1 - do we need error reporting? Devdatta Akhawe
• Re: Comments on Mixed Content Chris Palmer
• Re: [SRI] Towards v1 - do we need error reporting? Brian Smith
• Re: [SRI] Towards v1 - do we need fallback/noncanonical-src? Brian Smith

Wednesday, 10 December 2014

• Re: [MIX] PF comments on Mixed Content - accessible indication and user controls Brad Hill
• Comments on Mixed Content David Walp
• Re: [SRI] Towards v1 - do we need error reporting? Brad Hill
• Re: [SRI] Towards v1 - do we need fallback/noncanonical-src? Devdatta Akhawe
• Re: [SRI] Towards v1 - do we need error reporting? Devdatta Akhawe
• Re: [SRI] Towards v1 - do we need error reporting? Ben Toews
• [MIX] PF comments on Mixed Content - accessible indication and user controls Michael Cooper
• [SRI] Towards v1 - do we need error reporting? Frederik Braun
• [SRI] Towards v1 - do we need fallback/noncanonical-src? Frederik Braun

Tuesday, 9 December 2014

• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mark Watson
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Martin Thomson
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mike West
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Martin Thomson
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mike West
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mark Watson
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mike West
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mike West
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mike West
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Chris Palmer
• Re: [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mark Watson
• [POWER] New vs Legacy functionality (Re: "Requirements for Powerful Features" strawman.) Mike West
• Re: [REFERRER][CSP] Improving the Web Platform's Referrer Policy Mike West
• Re: Draft finding - "Transitioning the Web to HTTPS" Mike West

Thursday, 4 December 2014

• Call for Exclusions: Requirements for Powerful Features Coralie Mercier

Wednesday, 3 December 2014

• [REFERRER][CSP] Improving the Web Platform's Referrer Policy Brian Smith
• Re: [CSP3] Please define the encoding used for violation reports Boris Zbarsky
• Re: [CSP3] Please define the encoding used for violation reports Julian Reschke
• Re: [CSP3] Please define the encoding used for violation reports Boris Zbarsky
• Re: [CSP3] Please define the encoding used for violation reports Boris Zbarsky
• Re: [webappsec] Clarifying how CSP sandboxing applies to Workers, ServiceWorkers Anne van Kesteren
• Re: [CSP3] Please define the encoding used for violation reports Julian Reschke
• Re: [CSP3] Please define the encoding used for violation reports Julian Reschke

Tuesday, 2 December 2014

• Re: [webappsec] Dec 1, Thread 2: Powerful Features Wendy Seltzer
• Re: [webappsec] Dec 1, Thread 2: Powerful Features Mike West
• Re: [CSP3] Please define the encoding used for violation reports Boris Zbarsky
• Re: [webappsec] Dec 1, Thread 1: Rechartering Mounir Lamouri
• Re: [webappsec] Dec 1, Thread 1: Rechartering Brad Hill
• Re: [CSP3] Please define the encoding used for violation reports Julian Reschke
• [CSP3] Please define the encoding used for violation reports Boris Zbarsky
• Re: snapshots in CfC Re: CfC: Publish a FPWD of "Requirements for Powerful Features" chaals@yandex-team.ru

Monday, 1 December 2014

• Re: webappsec-ISSUE-69 (Overt channel control in CSP): Consider directives to manage postMessage and external navigation of iframes [CSP Next] Deian Stefan
• Re: [webappsec] Clarifying how CSP sandboxing applies to Workers, ServiceWorkers Brad Hill
• Re: [webappsec] Clarifying how CSP sandboxing applies to Workers, ServiceWorkers Deian Stefan
• [webappsec] Clarifying how CSP sandboxing applies to Workers, ServiceWorkers Brad Hill
• [webappsec] Dec 1, Thread 3: post-Last Call issues in CSP Level 2 Brad Hill
• [webappsec] Dec 1, Thread 2: Powerful Features Brad Hill
• [webappsec] Dec 1, Thread 1: Rechartering Brad Hill
• [webappsec] Cancel today's call? Brad Hill
• Re: snapshots in CfC Re: CfC: Publish a FPWD of "Requirements for Powerful Features" Brad Hill

Last message date: Tuesday, 30 December 2014 23:07:32 UTC