On 6/7/2011 5:52 PM, Adam Barth wrote:
On Tue, Jun 7, 2011 at 5:43 PM, Brian Smith<bsm...@mozilla.com> wrote:
Adam Barth wrote:
On 5/31/2011 8:24 AM, Brian Smith wrote:
We have also discussed blocking https+ws:// content completely in
our
WebSockets implementation, so that all WebSockets on a HTTPS page
must be
wss://. That way, we could avoid making mixed content problems any
worse.
Do you have a bug on file for that yet?
If you'd be willing to file a bug at bugs.webkit.org too (and CC me),
I can help make sure WebKit and Firefox end up with the same behavior
here.
Bugzilla Bug 662692
Chromium Issue 85271
WebKit Issue 62253
I wasn't sure which email address to use to CC you to the Chromium and WebKit
bugs.
Thanks!
Adam
Do we have consensus that this is something we want, both internally and
externally?
--Chris
_______________________________________________
dev-security mailing list
dev-security@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security
