-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development/documentation #1825
Conversation
|
else | ||
Client->>Server: Connect to port (default 443) | ||
|
||
Note over Client,Server: TLS handshake |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As TLS in principle is not connected to the WebSocket protocol itself I think we either remove that part or otherwise make that clear in the title and add some text to explain that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It denotes an alternative path as the diagram illustrates: WebSocket is on top of existing infrastructure, regular or TLS tunnelled (see https://www.rfc-editor.org/rfc/rfc6455.html#page-4 and https://www.rfc-editor.org/rfc/rfc6455.html#page-11). The diagram does not explain TLS in detail. Solid line delineated (blocks) text is to be interpreted as comment. Actually, the 'initial part of' the protocol starts with sending an HTTP upgrade request.
No description provided.