Apparently an announcement message is also en-route to the W3C WebApps
working group.
It's in their archives now..
fyi: Strict Transport Security specification
http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/1148.html
Please send feedback on the spec to the
In case you're still wondering about this topic, a draft of the spec
is now public:
http://lists.w3.org/Archives/Public/www-archive/2009Sep/att-0051/draft-hodges-strict-transport-sec-05.plain.html
Apparently an announcement message is also en-route to the W3C WebApps
working group.
Adam
On
On Thu, Sep 17, 2009 at 3:37 PM, Ben Goodger (Google) b...@chromium.org wrote:
Whoever added this UI, please remove it before I have to when I get
back next week.
Very well, reverting.
AGL
--~--~-~--~~~---~--~~
Chromium Developers mailing list:
Thanks!
On Thu, Sep 17, 2009 at 3:38 PM, Adam Langley a...@chromium.org wrote:
On Thu, Sep 17, 2009 at 3:37 PM, Ben Goodger (Google) b...@chromium.org
wrote:
Whoever added this UI, please remove it before I have to when I get
back next week.
Very well, reverting.
AGL
On Thu, Sep 17, 2009 at 3:31 PM, Adam Langley a...@chromium.org wrote:
On Thu, Sep 17, 2009 at 3:03 PM, Peter Kasting pkast...@google.com wrote:
It's disappointing to me that this change was made without any bug in the
bug database linked, and without any input from a member of the UI team,
It clears the list of hosts in StrictTransportSecurityState:
// StrictTransportSecurityState
//
// Tracks which hosts have enabled StrictTransportSecurityState. After a host
// enables StrictTransportSecurityState, then we refuse to talk to the host
// over HTTP, treat all certificate errors as
There's a published paper about it too:
http://www.adambarth.com/papers/2008/jackson-barth.pdf
On Thu, Sep 17, 2009 at 4:34 PM, Robert Sesek rse...@chromium.org wrote:
It clears the list of hosts in StrictTransportSecurityState:
// StrictTransportSecurityState
//
// Tracks which hosts have
