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

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

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 6 Jul 2015 17:17:28 +0200
Message-ID: <CADnb78h0C1H+dFpT0Lfhon20xSBmTyS48i8mytY08pXi3-NuZw@mail.gmail.com>
To: Mike West <mkwst@google.com>
Cc: Brian Smith <brian@briansmith.org>, "public-webappsec@w3.org" <public-webappsec@w3.org>, Dan Veditz <dveditz@mozilla.com>, Wendy Seltzer <wseltzer@w3.org>, Brad Hill <hillbrad@gmail.com>, Kristijan Burnik <burnik@google.com>, Ryan Sleevi <sleevi@google.com>
On Mon, Jul 6, 2015 at 5:09 PM, Mike West <mkwst@google.com> wrote:
> 1. If we drop the concept from MIX, it might be reasonable for Fetch to give
> examples of the cases in which a Response's HTTPS State might be "deprecated
> authentication".

Sure, file an issue?

> 2. WebSockets doesn't have a similar concept, which makes rewriting
> https://w3c.github.io/webappsec/specs/mixedcontent/#websockets-integration
> in terms of something else difficult.

Hmm yeah. WebSocket being kinda similar, but different, keeps biting
us. I wish the protocol was not in such an immutable state at the
IETF. Monkey patch?

Received on Monday, 6 July 2015 15:17:54 UTC

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