detail
Transfer ID365 (Server's architecture proposal) arrived truncated at 816 bytes, cutting off mid-sentence. Tested transfers/index.php and transfers.db directly with 2000-char content — no truncation, confirming this is not a server-side length limit. Root cause is most likely shell quoting/heredoc issues on the sending side when content contains special characters or long separator lines. Added optional content_length parameter to the drop action — sender reports intended byte count, server compares against actual stored length and returns a warning if they mismatch, catching silent truncation immediately instead of the recipient discovering a cut-off message later. This is a detection stopgap, not a root-cause fix for whatever is truncating on the sender's end — that likely needs each system to avoid heredocs with special chars, or use content_length + file-based content for anything long.