This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26386 - Since WebSocket is still in development, I propose in addition to "ws" and "wss", you also include " [...]
Summary: Since WebSocket is still in development, I propose in addition to "ws" and "w...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-19 13:37 UTC by contributor
Modified: 2014-07-19 16:44 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2014-07-19 13:37:23 UTC 
Specification: http://dev.w3.org/html5/websockets/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top
Referrer: 

Comment:
Since WebSocket is still in development, I propose in addition to "ws" and
"wss", you also include "tcp" and "udp" protocol headers that will allow for
connecting without a WebSocket handshake (raw connections). That would greatly
increase compatibility with existing services. This is currently a major
barrier to it's usage. A cryptography API would go along well with that, since
even if someone does write libraries in JavaScript, they would have major
performance issues. That would provide legacy support for mail servers that
require starttls.

Posted from: 94.190.193.97
User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2014-07-19 16:44:13 UTC 
Connecting without a handshake is a non-starter: it would be a security disaster.