W3C home > Mailing lists > Public > public-webappsec@w3.org > January 2015

Re: [MIX] HSTS, SW and mixed-content

From: Mike West <mkwst@google.com>
Date: Tue, 27 Jan 2015 16:50:33 +0100
Message-ID: <CAKXHy=dSqHhAuEDwDhZ1wLhfV1_pDT88g2o_+7sTY8raHvL6YQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Yves Lafon <ylafon@w3.org>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On Tue, Jan 27, 2015 at 4:22 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Jan 27, 2015 at 4:08 PM, Mike West <mkwst@google.com> wrote:
> > On Tue, Jan 27, 2015 at 3:49 PM, Yves Lafon <ylafon@w3.org> wrote:
> >> Is the characterization of the potentially secure/a priori insecure URLs
> >> done before or after applying HSTS URL rewriting?
> >
> > HSTS happens after mixed content checking. We've had a number of threads
> on
> > this, and there are reasonable arguments on both sides, but this is, I
> > think, where we've come down pretty solidly.
> Note that the editor of HSTS preferred it the other way around, but
> given that HSTS depends on a cache I think I've come around.

Note that all three shipping implementations (WebKit, Blink, Gecko) of HSTS
do the internal redirects after mixed content checking. :)

File a bug on Fetch to reorder them? Or are we going to wait until
> everything
> is written in terms of Fetch?


Mike West <mkwst@google.com>, @mikewest

Google Germany GmbH, Dienerstrasse 12, 80331 München,
Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der
Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)
Received on Tuesday, 27 January 2015 15:51:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:45 UTC