Re: CfC: Mixed Content to PR; deadline July 6th.

On Thu, Jul 30, 2015 at 10:24 AM, Anne van Kesteren <annevk@annevk.nl>
wrote:

> On Thu, Jul 30, 2015 at 9:59 AM, Mike West <mkwst@google.com> wrote:
> > Anne: I'm not sure what you meant by "I suppose it won't always disallow
> > that". When would we want to allow insecure responses to secure
> requests? I
> > don't think that's something we've discussed, nor is it something I
> think is
> > terribly appealing.
>
> If you have
>
>   <img src=https://example.com/x>
>
> and the service worker replies with
>
>   e.respondWith(fetch("http://unsafe.example/x", {mode:"no-cors"}))
>
> there's nothing really that prevents that.


Doesn't the set of `window` checks and associated copy behavior that we
discussed prevent this? That is, `fetch(e.request)` works because it copies
the window object rather than setting `no-window`. This code would set
`no-window`, and would therefore fail.

Have I misunderstood the algorithm in Fetch?

-mike

--
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.)