13526 2011-08-02 18:52:18 +0000 "One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if 2011-08-08 21:02:37 +0000 1 1 1 Unclassified WebAppsWG WebSocket API (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-websocket P3 normal --- 1 contributor ian ian mike public-webapps zcorpan public-webapps-bugzilla oldest_to_newest 52003 0 contributor 2011-08-02 18:52:18 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/network.html Multipage: http://www.whatwg.org/C#dom-websocket Complete: http://www.whatwg.org/c#dom-websocket Comment: "One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if everyone agree to do this Posted from: 85.227.153.57 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.50 54397 1 ian 2011-08-08 21:02:22 +0000 I guess we can try this. 54398 2 contributor 2011-08-08 21:02:37 +0000 Checked in as WHATWG revision r6385. Check-in comment: Prevent authors from shooting themselves in the foot here. Note that this blocks some legitimate use cases -- let me know if you think we should remove this restriction. It's easy to work around -- provide services over wss:// -- but some service providers might not bother. http://html5.org/tools/web-apps-tracker?from=6384&to=6385