mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 00:25:56 +03:00
[GH-ISSUE #1569] [BUG] Websocket Max Frame Size is 16Kb #1563
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1563
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NghiaTranUIT on GitHub (Mar 6, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1569
Originally assigned to: @NghiaTranUIT on GitHub.
Description
For some reason, the Websocket message is trimmed unexpectedly. We've checked that we set the MaxFrameSize is UInt32.max, but the WS Message is cut at 16Kb.
Steps to Reproduce
Current Behavior
The WS Message is trimmed
Expected Behavior
@invisible-debug commented on GitHub (Jun 27, 2024):
@NghiaTranUIT This is still critical. When is the fix planned?
@NghiaTranUIT commented on GitHub (Jun 28, 2024):
@invisible-debug I can't reproduce this bug. I tried to setup a NodeJS WS Server, and I can sent 5Mb JSON file without any problems.
Can you share with me what Backend library you're using? Python, Ruby and what the network lib is?
@invisible-debug commented on GitHub (Jun 28, 2024):
@NghiaTranUIT Try to send not just JSON, but a MESSAGE packet frame with a content length of more than 19000 characters.
Here is a link to the stomp protocol:
https://stomp.github.io/stomp-specification-1.2.html#MESSAGE
@invisible-debug commented on GitHub (Jun 28, 2024):
@NghiaTranUIT commented on GitHub (Jun 28, 2024):
@invisible-debug I guess I need to set up a sample Stomp Websocket Server to test it.
Since now, I just tested with a normal Websocket from NodeJS server and it works fine.
@NghiaTranUIT commented on GitHub (Jun 28, 2024):
@invisible-debug any chance to export your Websocket and share to us at support@proxyman.io ?
@invisible-debug commented on GitHub (Jun 28, 2024):
@NghiaTranUIT
Unfortunately, I cannot disclose the corporate json. But I tried to copy it from Charles, and then send it through the local mock server and Map Remote. And the bug is not reproducible :(
But there is one point that distinguishes a bug situation from a bug-free situation. Here is another screenshot where I showed it. This frame appears when the cursor hovers over the json body. Is this the reason why the json is not fully displayed?
@NghiaTranUIT commented on GitHub (Jun 28, 2024):
@invisible-debug thanks, it could be. I will try to disable it.
May I ask:
If yes, it's definitely a bug when displaying a JSON, not a bug when sending/receiving the WS message.
@invisible-debug commented on GitHub (Jun 28, 2024):
@NghiaTranUIT Yes, it is transmitted correctly. The problem is only in the display
@NghiaTranUIT commented on GitHub (Jun 29, 2024):
@invisible-debug here is the Beta build: https://download.proxyman.io/beta/Proxyman_5.5.0_Fix_monaco_editor_renders_a_long_line.dmg
I increase the limit to 50,000 (default is 10,000).
@invisible-debug commented on GitHub (Jun 29, 2024):
@NghiaTranUIT Unfortunately, this did not solve the problem. Only now the pop-up warning is not displayed. Content-length:18709. And why do I see the brackets in red? Because there are no closing brackets in the editor?
Maybe make a build without rendering? To exclude that affects the body