Repository navigation
Document browser connections over Bolt WebSocket and SSL - #1852
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents how browser apps connect to Memgraph: Bolt over WebSocket works on the Bolt port only without SSL, so a page served over HTTPS should query Memgraph through a backend. Also clarifies the SSL page's WebSocket tab, which read as if no WebSocket supported SSL; the log WebSocket on 7444 does.
Checked on Memgraph 3.13.0 (c829e614) in Docker:
ws://on 7687 without SSL: handshake succeeds.--bolt-cert-file/--bolt-key-fileset,ws://andwss://on 7687 both fail.wss://connects,ws://fails.Noticed, not fixed
Read by the release check, which fixes these in one PR per release. Fix an item if it's wrong; keep the heading and one line per item, starting with the page.
pages/database-management/ssl-encryption.mdx: Memgraph Lab tab says logs can't be viewed over SSL; Lab 2.1.2 release notes say this was fixed.pages/database-management/ssl-encryption.mdx: mgconsole tab passes--use-ssl=trueto thememgraph-mageimage in adocker runcommand, where it's a server flag, not an mgconsole flag; "mgconsol" typo.pages/database-management/ssl-encryption.mdx: PHP example is fenced aspython.pages/client-libraries/javascript.mdx: frontmatter title "JavaScript quick start" doesn't match the#heading "JavaScript client guide"; description starts with "Understand the dynamics".