public-webappsec@w3.org from February 2015 by date

Friday, 27 February 2015

• Re: why does plugin-types inherit to nested browsing contexts? Devdatta Akhawe
• Re: why does plugin-types inherit to nested browsing contexts? Mike West
• Re: Requiring Authenticated Origins for Geolocation API's: Status Joel Weinberger

Thursday, 26 February 2015

• Intent to deprecate: Insecure usage of powerful features Joel Weinberger
• Re: why does plugin-types inherit to nested browsing contexts? Devdatta Akhawe
• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) Eduardo' Vela\
• Re: why does plugin-types inherit to nested browsing contexts? Mike West
• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) Brian Smith
• Re: why does plugin-types inherit to nested browsing contexts? Devdatta Akhawe
• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) David Ross
• Re: why does plugin-types inherit to nested browsing contexts? Emily Stark

Wednesday, 25 February 2015

• Requiring Authenticated Origins for Geolocation API's: Status Mandyam, Giridhar
• Re: why does plugin-types inherit to nested browsing contexts? Brad Hill
• why does plugin-types inherit to nested browsing contexts? Emily Stark

Monday, 23 February 2015

• Re: Private Devices and IoT (was Proposal: Marking HTTP As Non-Secure) Adam Langley

Wednesday, 25 February 2015

• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) Eduardo' Vela\
• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) Brian Smith
• Re: Fetch, MSE, and MIX Ryan Sleevi
• Re: Fetch, MSE, and MIX Brian Smith
• Re: [MIX] Require HTTPS scripts to be able to anything HTTP scripts can do. Brad Hill
• Re: [MIX] Require HTTPS scripts to be able to anything HTTP scripts can do. Tim Berners-Lee
• Re: CORS performance Anne van Kesteren

Tuesday, 24 February 2015

• Re: CORS performance Jonas Sicking
• Re: BIKESHED: Rename "Powerful features"? Jeffrey Yasskin
• Re: CORS performance Anne van Kesteren

Monday, 23 February 2015

• Re: draft minutes from 23-Feb teleconference available Francois Marier
• Re: draft minutes from 23-Feb teleconference available Brad Hill
• draft minutes from 23-Feb teleconference available Brad Hill
• last charter update Brad Hill
• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Brad Hill
• webappsec-ACTION-214: Ask mozilla ac rep about the current status of their charter objections Web Application Security Working Group Issue Tracker
• [webappsec] Teleconference Agenda, 23-Feb-2015 Brad Hill
• Re: BIKESHED: Rename "Powerful features"? Yan Zhu
• Re: CORS performance Jonas Sicking
• Re: CORS performance Anne van Kesteren
• Re: CORS performance proposal Jonas Sicking
• Re: CORS performance proposal Jonas Sicking
• Re: CORS performance Jonas Sicking
• Re: Private Devices and IoT (was Proposal: Marking HTTP As Non-Secure) Jeffrey Walton
• Re: Upgrade mixed content URLs through HTTP header =JeffH
• RE: BIKESHED: Rename "Powerful features"? Crispin Cowan
• Re: CORS performance Henri Sivonen
• Re: BIKESHED: Rename "Powerful features"? Mike West
• Re: BIKESHED: Rename "Powerful features"? Jeffrey Yasskin
• Re: BIKESHED: Rename "Powerful features"? Jeffrey Yasskin
• Re: BIKESHED: Rename "Powerful features"? Mike West
• [webappsec] agenda - coming soon Brad Hill

Sunday, 22 February 2015

• Private Devices and IoT (was Proposal: Marking HTTP As Non-Secure) Jeffrey Walton
• Re: CORS performance proposal Anne van Kesteren

Saturday, 21 February 2015

• Re: CORS performance proposal Martin Thomson
• Re: CORS performance proposal Anne van Kesteren
• Re: BIKESHED: Rename "Powerful features"? Oda, Terri

Friday, 20 February 2015

• Re: Fetch, MSE, and MIX Ryan Sleevi
• Re: Fetch, MSE, and MIX Brian Smith
• Re: CORS performance proposal Jonas Sicking
• Re: Fetch, MSE, and MIX Brad Hill
• Re: CORS explained simply Brad Hill
• Re: Fetch, MSE, and MIX Aaron Colwell
• Re: CORS explained simply Odin Hørthe Omdal
• Re: CORS explained simply Anne van Kesteren
• Re: CORS explained simply chaals@yandex-team.ru
• Re: CORS performance proposal Anne van Kesteren
• Re: CORS explained simply Anne van Kesteren
• Fetch, MSE, and MIX Ryan Sleevi
• Re: CORS performance proposal Bjoern Hoehrmann
• Re: CORS performance proposal Martin Thomson

Thursday, 19 February 2015

• Re: CORS performance Jonas Sicking
• Re: CORS performance proposal Bjoern Hoehrmann
• Re: CORS explained simply Brad Hill
• Re: CORS performance proposal Brian Smith
• CORS explained simply henry.story@bblfish.net
• Re: CORS performance Bjoern Hoehrmann
• Re: CORS performance henry.story@bblfish.net
• Re: CORS performance Martin Thomson
• Re: CORS performance proposal Martin Thomson
• Re: CORS performance Brad Hill
• Re: CORS performance proposal Jonas Sicking
• Re: CORS performance Jonas Sicking
• Re: CORS performance Jonas Sicking
• Re: CORS performance proposal Dale Harvey
• Re: CORS performance James M Snell
• Re: CORS performance Brian Smith
• Re: CORS performance Dale Harvey
• Re: CORS performance Dale Harvey
• CORS performance proposal Anne van Kesteren
• Re: CORS performance Brian Smith
• Re: CORS performance Dale Harvey
• Re: CORS performance Brian Smith
• Re: CORS performance Dale Harvey
• Re: CORS performance Brian Smith
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Dale Harvey
• Re: CORS performance Brian Smith
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Brian Smith
• Re: CORS performance Mike West
• Re: BIKESHED: Rename "Powerful features"? Alex Russell

Wednesday, 18 February 2015

• RE: BIKESHED: Rename "Powerful features"? Crispin Cowan
• Re: BIKESHED: Rename "Powerful features"? Mark Watson
• RE: BIKESHED: Rename "Powerful features"? Crispin Cowan
• Re: BIKESHED: Rename "Powerful features"? Jeffrey Yasskin
• Re: Follow-up to TAG meeting on Powerful Features Brad Hill
• Re: BIKESHED: Rename "Powerful features"? Yan Zhu
• Re: BIKESHED: Rename "Powerful features"? Mark Watson
• Re: BIKESHED: Rename "Powerful features"? Eduardo' Vela\
• Re: BIKESHED: Rename "Powerful features"? Mike West
• Re: BIKESHED: Rename "Powerful features"? Michal Zalewski
• Re: BIKESHED: Rename "Powerful features"? Mark Watson
• BIKESHED: Rename "Powerful features"? Mike West
• Re: CfC: Transition Mixed Content to CR; deadline Feb 23rd. Mike West
• Re: Service Workers and MIX (was Re: MIX: Exiting last call?) Mike West
• Re: Follow-up to TAG meeting on Powerful Features Mike West
• Re: Follow-up to TAG meeting on Powerful Features Wendy Seltzer
• Re: CORS performance Eric Mill

Tuesday, 17 February 2015

• RE: Upgrade mixed content URLs through HTTP header David Walp
• Re: Upgrade mixed content URLs through HTTP header Ryan Sleevi
• Re: Upgrade mixed content URLs through HTTP header Tom Ritter
• Re: Signed CSP Yan Zhu
• Re: Follow-up to TAG meeting on Powerful Features Yan Zhu
• Re: CORS performance Bjoern Hoehrmann
• Re: CORS performance Devdatta Akhawe
• Re: CORS performance Brad Hill
• Re: CORS performance Anne van Kesteren
• Re: CORS performance Bjoern Hoehrmann
• CORS performance Anne van Kesteren
• Re: Service Workers and MIX (was Re: MIX: Exiting last call?) Brian Smith
• Re: CfC: Transition Mixed Content to CR; deadline Feb 23rd. Brian Smith
• Re: Follow-up to TAG meeting on Powerful Features Brad Hill
• RE: Follow-up to TAG meeting on Powerful Features Crispin Cowan
• Re: Follow-up to TAG meeting on Powerful Features Mark Watson
• Re: Follow-up to TAG meeting on Powerful Features Daniel Appelquist

Monday, 16 February 2015

• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Mike West
• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Deian Stefan
• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Mike West
• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Deian Stefan
• Follow-up to TAG meeting on Powerful Features Wendy Seltzer
• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Mike West
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Mike West
• CfC: Transition Mixed Content to CR; deadline Feb 23rd. Mike West
• RE: Signed CSP Crispin Cowan
• Re: Signed CSP Scott Arciszewski
• Re: Signed CSP Michal Zalewski
• Re: Signed CSP Scott Arciszewski
• Re: Signed CSP Scott Arciszewski
• RE: Signed CSP Crispin Cowan

Sunday, 15 February 2015

• Re: Signed CSP Scott Arciszewski
• RE: Signed CSP Crispin Cowan
• Re: Signed CSP Scott Arciszewski
• RE: Signed CSP Crispin Cowan
• Signed CSP Scott Arciszewski

Friday, 13 February 2015

• Re: [Referrer] Adding a referrer attribute delivery mechanism Brian Smith
• Re: [Referrer] Adding a referrer attribute delivery mechanism Brian Smith
• Re: [Referrer] Adding a referrer attribute delivery mechanism Scott Beardsley
• Re: UPGRADE: Feature detection? Mike West
• Re: [Referrer] Adding a referrer attribute delivery mechanism Mike West

Thursday, 12 February 2015

• RE: [Referrer] Adding a referrer attribute delivery mechanism Scott Beardsley

Friday, 13 February 2015

• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) Eduardo' Vela\
• Re: WebAppSec re-charter status Eduardo' Vela\
• Re: WebAppSec re-charter status Anne van Kesteren
• Re: WebAppSec re-charter status Bjoern Hoehrmann
• Re: WebAppSec re-charter status Eduardo' Vela\
• Re: [Referrer] Adding a referrer attribute delivery mechanism Francois Marier
• Re: [Referrer] Adding a referrer attribute delivery mechanism Devdatta Akhawe
• Re: [Referrer] Adding a referrer attribute delivery mechanism Francois Marier
• Re: [Referrer] Adding a referrer attribute delivery mechanism Devdatta Akhawe
• Re: WebAppSec re-charter status Brad Hill
• Re: WebAppSec re-charter status Bjoern Hoehrmann
• Re: WebAppSec re-charter status Bjoern Hoehrmann
• RfC: Manifest for web application; review deadline March 5 Arthur Barstow

Thursday, 12 February 2015

• Re: WebAppSec re-charter status David Ross
• Re: WebAppSec re-charter status Eduardo' Vela\
• Re: Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) David Ross
• Re: WebAppSec re-charter status Anne van Kesteren
• Entry Point Regulation vs Simpler Solutions (was Re: WebAppSec re-charter status) Brian Smith
• Re: WebAppSec re-charter status Eduardo' Vela\
• Re: WebAppSec re-charter status Anne van Kesteren
• Re: WebAppSec re-charter status Eduardo' Vela\
• Re: WebAppSec re-charter status Anne van Kesteren
• Re: WebAppSec re-charter status David Ross

Wednesday, 11 February 2015

• RE: [Unbearable] IETF seeking feedback on proposed "Token Binding" Working Group Andrei Popov

Thursday, 12 February 2015

• Re: UPGRADE: Feature detection? Julian Reschke

Wednesday, 11 February 2015

• Re: UPGRADE: Feature detection? Daniel Kahn Gillmor

Thursday, 12 February 2015

• Re: UPGRADE: Feature detection? Bjoern Hoehrmann
• Re: UPGRADE: Feature detection? Mike West
• Re: UPGRADE: Feature detection? Martin Thomson
• Re: Credentials Management API & multiple-credentials. Mike West
• Re: [Referrer] Adding a referrer attribute delivery mechanism Mike West
• Re: Proposal: A pinning mechanism for CSP? Mike West
• Re: [Referrer] Adding a referrer attribute delivery mechanism Anne van Kesteren
• Re: [Referrer] Adding a referrer attribute delivery mechanism Anne van Kesteren
• Re: [Referrer] Adding a referrer attribute delivery mechanism Mike West
• Re: WebAppSec re-charter status Anne van Kesteren
• Re: [Referrer] Adding a referrer attribute delivery mechanism Mike West
• Re: UPGRADE: Feature detection? Mike West
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Mike West
• Re: [Referrer] Adding a referrer attribute delivery mechanism Anne van Kesteren
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Mike West
• Re: UPGRADE: Feature detection? Martin Thomson
• Re: [Referrer] Adding a referrer attribute delivery mechanism Martin Thomson
• Re: UPGRADE: Feature detection? Mike West
• Re: UPGRADE: Goals? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Mike West
• Re: [Referrer] Adding a referrer attribute delivery mechanism Brian Smith
• Re: [Referrer] Adding a referrer attribute delivery mechanism Martin Thomson
• Re: [Referrer] Adding a referrer attribute delivery mechanism Brian Smith
• Re: [Referrer] Adding a referrer attribute delivery mechanism Jim Manico
• [Referrer] Adding a referrer attribute delivery mechanism Francois Marier

Wednesday, 11 February 2015

• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Brian Smith
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Brian Smith
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Brian Smith
• Re: WebAppSec re-charter status David Ross
• Re: Proposal: A pinning mechanism for CSP? Brian Smith
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Brian Smith
• Re: UPGRADE: Feature detection? Jacob Hoffman-Andrews
• Re: UPGRADE: Feature detection? Daniel Kahn Gillmor
• Re: UPGRADE: Goals? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Daniel Kahn Gillmor
• Re: [Unbearable] IETF seeking feedback on proposed "Token Binding" Working Group Anne van Kesteren
• RE: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Crispin Cowan
• Re: UPGRADE: Goals? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Brad Hill
• Re: Process? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Brad Hill
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Daniel Kahn Gillmor
• Re: UPGRADE: Feature detection? Mike West
• Re: UPGRADE: Feature detection? Anne van Kesteren
• UPGRADE: Feature detection? Mike West
• Re: Process? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Mike West
• Re: Process? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Wendy Seltzer
• Process? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Mike West
• UPGRADE: Goals? (was Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th.) Mike West
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Mike West
• Re: IETF seeking feedback on proposed "Token Binding" Working Group Anne van Kesteren
• Re: CfC approved: CSP Level 2 to Candidate Recommendation Brian Smith
• Re: CfC: Transition CSP2 to CR. Bjoern Hoehrmann
• IETF seeking feedback on proposed "Token Binding" Working Group Arthur Barstow
• Re: CfC: Transition CSP2 to CR. Brian Smith
• Re: CfC: Transition CSP2 to CR. Bjoern Hoehrmann
• Re: CfC: Transition CSP2 to CR. Brian Smith
• Re: CfC approved: CSP Level 2 to Candidate Recommendation Mike West
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Mike West
• Re: referrer spec and backwards compatibility Mike West
• Re: CfC approved: CSP Level 2 to Candidate Recommendation Bjoern Hoehrmann

Tuesday, 10 February 2015

• Re: CfC approved: CSP Level 2 to Candidate Recommendation Daniel Veditz
• Credentials Management API & multiple-credentials. rektide@voodoowarez.com
• Always on SSL Ben Wilson
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Tanvi Vyas
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Brad Hill
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Jim Manico
• RE: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Crispin Cowan
• Re: referrer spec and backwards compatibility Devdatta Akhawe
• Re: CfC approved: CSP Level 2 to Candidate Recommendation Brad Hill
• Re: CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Mike West
• CfC to publish FPWD of "Upgrade Insecure Resources"; Deadline Feb 17th. Mike West
• Re: CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Mike West
• Re: referrer spec and backwards compatibility Mike West
• Re: CfC approved: CSP Level 2 to Candidate Recommendation Mike West
• Re: CfC: Transition CSP2 to CR. Mike West

Monday, 9 February 2015

• CfC approved: CSP Level 2 to Candidate Recommendation Brad Hill
• Re: CfC: Transition CSP2 to CR. Francois Marier
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Jim Manico
• webappsec-ACTION-213: Reply to brian smith re: csp2 to cr Web Application Security Working Group Issue Tracker
• webappsec-ACTION-212: Issue cfc to take mixed content to cr Web Application Security Working Group Issue Tracker
• RE: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Crispin Cowan
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Jim Manico
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Brad Hill
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Jim Manico
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Brad Hill
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Devdatta Akhawe
• Re: referrer spec and backwards compatibility Devdatta Akhawe
• Re: WebAppSec re-charter status Devdatta Akhawe
• Re: CfC: Transition CSP2 to CR. Bjoern Hoehrmann
• Re: Proposal: A pinning mechanism for CSP? Mike West
• Re: Proposal: A pinning mechanism for CSP? Brian Smith
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Jim Manico
• Re: iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Mike West
• Re: CfC: Transition CSP2 to CR. Mike West
• Re: CfC: Transition CSP2 to CR. Brian Smith
• iframe sandbox for third-party widgets and ads (was Re: [CSP] Clarifications on nonces) Brian Smith
• Re: [CSP] Clarifications on nonces Brian Smith
• Re: [CSP] Clarifications on nonces Mike West
• Re: [CSP] Clarifications on nonces Jim Manico
• Re: [CSP] Clarifications on nonces Mike West
• Re: referrer spec and backwards compatibility Mike West
• Re: CfC: Transition CSP2 to CR. Mike West
• Re: Proposal: A pinning mechanism for CSP? Mike West
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: WebAppSec re-charter status Deian Stefan
• Re: [CSP] Clarifications on nonces Brian Smith
• Re: WebAppSec re-charter status Devdatta Akhawe
• referrer spec and backwards compatibility Devdatta Akhawe
• Re: WebAppSec re-charter status Deian Stefan
• Re: [SRI] unsupported hashes and invalid metadata Jim Manico
• Re: [SRI] unsupported hashes and invalid metadata Devdatta Akhawe
• Re: [SRI] unsupported hashes and invalid metadata Brian Smith
• Re: WebAppSec re-charter status Devdatta Akhawe
• Re: [SRI] unsupported hashes and invalid metadata Devdatta Akhawe
• Re: [SRI] unsupported hashes and invalid metadata Brian Smith
• Re: [SRI] unsupported hashes and invalid metadata Brian Smith
• Issues with reflected-xss (was Re: CfC: Transition CSP2 to CR.) Brian Smith
• Re: WebAppSec re-charter status Martin Thomson
• Re: CfC: Transition CSP2 to CR. Brian Smith
• Re: WebAppSec re-charter status Deian Stefan
• Re: CfC: Transition CSP2 to CR. Devdatta Akhawe
• Re: WebAppSec re-charter status Devdatta Akhawe
• Re: CfC: Transition CSP2 to CR. Francois Marier
• Re: [SRI] unsupported hashes and invalid metadata Francois Marier
• Re: WebAppSec re-charter status Deian Stefan
• [webappsec] Teleconference Agenda, 09-Feb-2015 Brad Hill
• Re: WebAppSec re-charter status Martin Thomson

Sunday, 8 February 2015

• Re: WebAppSec re-charter status Brad Hill
• Re: [SRI] unsupported hashes and invalid metadata Devdatta Akhawe

Saturday, 7 February 2015

• Re: CfC: Transition CSP2 to CR. Brad Hill
• Re: CfC: Transition CSP2 to CR. Mike West
• Re: Proposal: A pinning mechanism for CSP? Eric Mill
• Re: CfC: Transition CSP2 to CR. Bjoern Hoehrmann
• Re: CfC: Transition CSP2 to CR. Mike West
• Re: Proposal: A pinning mechanism for CSP? Mike West

Friday, 6 February 2015

• RE: Upgrade mixed content URLs through HTTP header Xiaoyin Liu
• Re: WebAppSec re-charter status Jeffrey Yasskin
• Re: Upgrade mixed content URLs through HTTP header Tanvi Vyas
• Re: CfC: Transition CSP2 to CR. Brian Smith
• Re: Proposal: A pinning mechanism for CSP? Brian Smith
• Re: WebAppSec re-charter status Anne van Kesteren
• Re: CfC: Transition CSP2 to CR. Mike West
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header John Wong
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Devdatta Akhawe
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Devdatta Akhawe
• Re: [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Peter Eckersley

Thursday, 5 February 2015

• Re: [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Daniel Kahn Gillmor
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Anne van Kesteren
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Brian Smith
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Brad Hill
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Chris Palmer
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Martin Thomson
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Brad Hill
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Peter Eckersley
• Re: WebAppSec re-charter status Deian Stefan
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Oda, Terri
• Re: WebAppSec re-charter status Alex Russell
• Re: WebAppSec re-charter status Bjoern Hoehrmann
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Frederik Braun
• Re: WebAppSec re-charter status Mike West
• Re: [CSP] Dynamic CSP Mike West
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Mike West
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Mike West

Wednesday, 4 February 2015

• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Brad Hill
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Wendy Seltzer
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Martin Thomson
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Peter Eckersley
• Re: [CSP] Dynamic CSP Deian Stefan
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Arthur Barstow
• Re: [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Jacob Hoffman-Andrews
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Mike West
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Anne van Kesteren
• Re: [CSP] Dynamic CSP Daniel Kahn Gillmor
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Brad Hill
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Mike West
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Wendy Seltzer
• Re: [CSP] Dynamic CSP Mike West
• Re: Asynchronous decision making (Re: WebAppSec re-charter status) Mike West
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: [CSP] Dynamic CSP Daniel Kahn Gillmor
• Re: Upgrade mixed content URLs through HTTP header Emily Stark
• Asynchronous decision making (Re: WebAppSec re-charter status) Frederik Braun
• Re: WebAppSec re-charter status chaals@yandex-team.ru
• WebAppSec re-charter status Wendy Seltzer
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Peter Eckersley
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Martin Thomson
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Anne van Kesteren
• Re: [CSP] Dynamic CSP Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Mike West

Tuesday, 3 February 2015

• Re: Upgrade mixed content URLs through HTTP header Emily Stark

Wednesday, 4 February 2015

• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Mike West
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Eric Mill
• Re: Upgrade mixed content URLs through HTTP header Daniel Kahn Gillmor
• Re: [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Tom Ritter
• Re: Upgrade mixed content URLs through HTTP header Jacob Hoffman-Andrews
• Re: Upgrade mixed content URLs through HTTP header Tom Ritter
• Re: CSP: Drop IP-matching? (was Re: [CSP] URI/IRI normalization and comparison) Oda, Terri
• Re: Upgrade mixed content URLs through HTTP header Austin William Wright

Tuesday, 3 February 2015

• RE: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Crispin Cowan
• Re: Upgrade mixed content URLs through HTTP header David Bruant
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Mike West
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Peter Eckersley
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Eduardo' Vela\
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Anne van Kesteren
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Anne van Kesteren
• Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Eduardo' Vela\
• An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) Mike West
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Wendy Seltzer
• Re: Upgrade mixed content URLs through HTTP header Peter Eckersley
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Peter Eckersley
• Re: Upgrade mixed content URLs through HTTP header Ryan Sleevi
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Peter Eckersley
• Re: Upgrade mixed content URLs through HTTP header Peter Eckersley
• Re: Upgrade mixed content URLs through HTTP header Peter Eckersley
• [MIX] 4 possible solutions to the problem of Mixed Content Blocking stalling HTTPS deployment Peter Eckersley
• Re: Upgrade mixed content URLs through HTTP header Eduardo' Vela\
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Eduardo' Vela\
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Eduardo' Vela\
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren

Monday, 2 February 2015

• RE: [CSP] Dynamic CSP Crispin Cowan
• Re: Upgrade mixed content URLs through HTTP header Daniel Kahn Gillmor
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Jim Manico
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Jim Manico
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Re: Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Upgrade mixed content URLs through HTTP header Mike West
• Upgrade mixed content URLs through HTTP header Anne van Kesteren
• Re: Server Certificates, Internal Names, and Browser support after October 2016 Tom Ritter
• Re: [CSP] Dynamic CSP Yoav Weiss
• CfC to publish FPWD of CSP Pinning; deadline Feb. 9th Mike West
• Re: Proposal: A pinning mechanism for CSP? Mike West
• Server Certificates, Internal Names, and Browser support after October 2016 Jeffrey Walton

Sunday, 1 February 2015

• Re: Proposal: A pinning mechanism for CSP? Daniel Veditz

Last message date: Friday, 27 February 2015 18:21:56 UTC