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

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?


https://www.w3.org/Bugs/Public/show_bug.cgi?id=27909

--
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
Flores
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)