Azreyo/Carbon
1
1
Fork 0
Code Actions Packages Projects Releases Wiki Activity

fix: Remove unnecessary max_frame_size calculation in websocket handling
Some checks failed
C/C++ CI / build (push) Failing after 5m19s
Details
C/C++ CI / test (push) Has been skipped
Details
C/C++ CI / code-quality (push) Failing after 1m10s
Details
C/C++ CI / security-scan (push) Failing after 1m2s
Details
CI Pipeline / build (push) Failing after 56s
Details
CI Pipeline / test (push) Has been skipped
Details
CI Pipeline / security-scan (push) Failing after 50s
Details
CI Pipeline / code-quality (push) Failing after 1m10s
Details
CI Pipeline / docker-build (push) Failing after 3m53s
Details

Browse Source
This commit is contained in:
Azreyo
2025-12-20 22:33:57 +01:00
parent f433ae55e4
commit 8d16e539bb
1 changed files with 0 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/websocket.c
View File

@@ -287,12 +287,6 @@ int ws_send_frame(ws_connection_t* conn, uint8_t opcode, const uint8_t* payload,
return -1; return -1;
} }
size_t max_frame_size = 10 + payload_len;
if (max_frame_size > 65536)
{
max_frame_size = 65536;
}
uint8_t buffer[65536]; uint8_t buffer[65536];
// Limit payload to avoid overflow (65536 - 10 bytes for max header) // Limit payload to avoid overflow (65536 - 10 bytes for max header)