From 61690c368db1709c1bfda58a0a4202a7a846575e Mon Sep 17 00:00:00 2001 From: thelittlefox Date: Thu, 7 Dec 2023 08:51:05 +0800 Subject: [PATCH] Updated Enabling WebSocket notifications (markdown) --- Enabling-WebSocket-notifications.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Enabling-WebSocket-notifications.md b/Enabling-WebSocket-notifications.md index 26a4da0..144c2e5 100644 --- a/Enabling-WebSocket-notifications.md +++ b/Enabling-WebSocket-notifications.md @@ -29,8 +29,6 @@ Example configurations are included in [[Proxy examples|proxy-examples]]. Testing if a connection is working correctly can be done in two ways: 1. Open the developer tools of your browser, go to the network tab and filter for `WS`/`WebSockets`. Logout or refresh the page and login again and you you should see a 101 response for the upgraded WebSocket connection. If you click on that line you should be able to see the messages. If you do not get the status code 101 on `/notifications/hub` then something is configured incorrectly. -Messages will be shown in the console window of your browser: - -`[2023-12-01T00:00:00.000Z] Information: WebSocket connected to wss://HOST_NAME/notifications/hub?access_token=eyJ0eX......` +Messages will be shown in the console window of your browser:`[2023-12-01T00:00:00.000Z] Information: WebSocket connected to wss://HOST_NAME/notifications/hub?access_token=eyJ0eX......` 2. Open two different browsers or an incognito/private window. Login into your account on both. Either create a new entry, or rename the cipher in one, and that should instantly change also in the other.