Skip to content
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

Merged
merged 16 commits into from
Jan 14, 2025
Merged

Development/documentation #1825

merged 16 commits into from
Jan 14, 2025

Conversation

msieben
Copy link
Contributor

@msieben msieben commented Jan 13, 2025

No description provided.

Copy link

github-actions bot commented Jan 13, 2025

PR Preview Action v1.1.1-25-g59e77e4
🛬 Preview removed because the pull request was closed.
2025-01-14 08:43 UTC

else
Client->>Server: Connect to port (default 443)

Note over Client,Server: TLS handshake
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@msieben msieben merged commit 2eafff8 into master Jan 14, 2025
80 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants