Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header)

I see, I thought that had changed recently (there was a discussion about
sites using CORS breaking when upgrading to SSL and that this shouldn't be
allowed). I guess this is OK then.

On Tue, Feb 3, 2015 at 4:47 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Feb 3, 2015 at 4:40 PM, Eduardo' Vela" <Nava> <evn@google.com>
> wrote:
> > I was hoping this would work as a *-src directive, since there are sites
> > that will (for ever) need to fetch http:// resources over XHR (eg,
> > Chromecast).
>
> That is blocked already. (XMLHttpRequest (CORS, more generally) does
> not allow for Mixed Content.) What am I missing?
>
>
> --
> https://annevankesteren.nl/
>