Open
Conversation
arthurwolf
reviewed
Apr 14, 2026
| * Attempt to download a file by clicking on the three dots next to the file, and selecting ‘Download’. You should see traffic in the 'Network' tab of the inspector. The results of your attempt do not matter. | ||
| * In the inspector, Click on the 'File' or 'Name' column header once. This should sort the requests that were sent. | ||
| * If there is not a 'Method' column shown, please right click on 'Name' or 'File', and select 'Method' to make it visible. | ||
| * Look for a file who’s name starts with “3-4” |
There was a problem hiding this comment.
Suggested change
| * Look for a file whose name starts with “3-4” |
arthurwolf
reviewed
Apr 14, 2026
| * Make a note of the full URL. It should point to `nginz-ssl.<domain>` — this is Wire's WebSocket endpoint. If it is pointing elsewhere, note that down. | ||
| * In the detail pane, look for a **Messages** tab (Chrome/Edge) or **Response** tab (Firefox). Select it. | ||
| * You should see a stream of messages being exchanged between the client and the server. At this point the list may be empty or contain only the initial handshake — that is fine. | ||
| * **Wait Patiently.** The backend sends a ping to the client every 30 seconds, and the client responds with a pong. You are waiting to observe this exchange. Allow at least 60 seconds — long enough to be confident you would have seen at least one ping/pong cycle if the connection were healthy. |
There was a problem hiding this comment.
Suggested change
| * **Wait Patiently.** The backend sends a ping to the client every 30 seconds, and the client responds with a pong. You are waiting to observe this exchange. Allow at least 60 seconds — long enough to be confident you would have seen at least one ping/pong cycle if the connection were healthy. | |
| * **Wait Patiently.** The backend sends a ping to the client every 20 seconds, and the client responds with a pong. You are waiting to observe this exchange. Allow at least 60 seconds — long enough to be confident you would have seen at least one ping/pong cycle if the connection were healthy. |
Looked in the browser at the actual ping/pongs, and it looks like the interval is actually 20 seconds for app.wire.com, maybe it's configurable?
There was a problem hiding this comment.
Also I think it's the client not the server that sends this ping (there are actually two pings, one sent by the server every 15 seconds (websocket control frames) and one sent by the client every 20 seconds (application level data messages), the only one you "see" in the browser dev tools is the client-sent one).
For more details see this report: https://gist.github.com/arthurwolf/201c9b64f040ee3680ac3222479450ea
arthurwolf
reviewed
Apr 14, 2026
| * **Wait Patiently.** The backend sends a ping to the client every 30 seconds, and the client responds with a pong. You are waiting to observe this exchange. Allow at least 60 seconds — long enough to be confident you would have seen at least one ping/pong cycle if the connection were healthy. | ||
| * In Chrome and Edge, ping frames are shown with an upward arrow and a payload of the ping data; pong frames are shown with a downward arrow. They may also be labelled explicitly as 'ping' and 'pong' depending on browser version. | ||
| * In Firefox, the frames are listed in the Response tab with their type and direction noted in the Type column. | ||
| > NOTE: A healthy connection will show a ping from the server followed shortly by a pong from the client, repeating approximately every 30 seconds. |
There was a problem hiding this comment.
Suggested change
| > NOTE: A healthy connection will show a ping from the server followed shortly by a pong from the client, repeating approximately every 30 seconds. | |
| > NOTE: A healthy connection will show a ping from the server followed shortly by a pong from the client, repeating approximately every 20 seconds. |
Looked in the browser at the actual ping/pongs, and it looks like the interval is actually 20 seconds for app.wire.com, maybe it's configurable?
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
2 participants
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.
Change type
Basic information
Testing
Tracking