Fragment: Clarify fragment behavior

This commit is contained in:
Fangliding
2026-09-07 01:17:32 +08:00
parent d5d0912d19
commit 3b278ad42c
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -160,7 +160,7 @@ Controls outgoing TCP fragmentation. In some cases it can deceive censorship sys
`"lengths"`: fragment size in bytes.
The n-th element of the array specifies the expected length of the n-th fragment split from the current packet being processed; the last element keeps applying to all subsequent fragments split from that packet. Entries other than the last may be `0`; when `0` is selected, no fragment is split out for that round — it just idles and waits out the corresponding delay before the next one.
The n-th element of the array specifies the expected length of the n-th fragment split from the current packet being processed; the last element keeps applying to all subsequent fragments split from that packet. Entries other than the last may be `0` (otherwise it causes infinite idling); for TCP stream slicing, it behaves as sending no data, while for tlshello, it behaves as sending an RFC-violating empty TLS record (tolerated by some implementations, but not Golang).
`"delays"`: interval between fragments in milliseconds.