Correct packet description #41495
Correct packet description #41495
Conversation
chrisdavidmills
requested review from
hamishwillee
and removed request for
a team
|
Preview URLs Flaws (1)URL:
(comment last updated: 2025-10-13 11:58:19) |
|
|
||
| - They are sometimes dropped or corrupted, and when this happens, it's quicker and easier for the client to request the missing packets rather than an entire file. | ||
| - The packets can be routed along different paths, making the transmission as efficient as possible and reducing the possibility of slowing down the network, especially when many users are requesting the same resource simultaneously. The packets may arrive out of sequence, but the client can use the information in the packet headers to make sure they are assembled in the correct order. | ||
| - It is harder to steal user data when transmitted in packets, as each packet contains minimal data and is transmitted separately. |
There was a problem hiding this comment.
This seems unlikely to me. Hard to imagine an attack that steals one packet but not more.
There was a problem hiding this comment.
It seemed kinda unlikely to me as well, but I read quite a few packet definitions elsewhere that mentioned something along these lines.
I mean, it sounds vaguely plausible from the outset, but knowing what I know about how web security breaches occur, it probably isn't worth bringing up. I put it here in case anyone else had any thoughts. Happy to delete.
There was a problem hiding this comment.
Wondering if there's anyone else we can consult—@hamishwillee?
2 participants
Description
The description of packets in How the web works is inaccurate. This PR aims to fix it.
Motivation
Additional details
Related issues and pull requests
Fixes #41479.