Re: An HTTP->HTTPS upgrading strawman. (was Re: Upgrade mixed content URLs through HTTP header) from Anne van Kesteren on 2015-02-03 (public-webappsec@w3.org from February 2015)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 3 Feb 2015 16:44:39 +0100
To: "Eduardo' Vela <Nava>" <evn@google.com>
Cc: Mike West <mkwst@google.com>, Ryan Sleevi <sleevi@google.com>, Wendy Seltzer <wseltzer@w3.org>, Adam Langley <agl@google.com>, WebAppSec WG <public-webappsec@w3.org>, Peter Eckersley <pde@eff.org>
Message-ID: <CADnb78iri==YxXaxvHcbFwacbcEzBK8CXYtETKVP0=+LxJQDdA@mail.gmail.com>

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 sounds like outside the scope of this specification as XMLHttp


-- 
https://annevankesteren.nl/

Received on Tuesday, 3 February 2015 15:45:08 UTC