itwanger / itwanger/toBeBetterJavaer
network文档关于"为什么要TCP 三次握手"的 SYN 字段存在混淆错误
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.7k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
您好，我在阅读计算机网络文档时发现一处关于 TCP 三次握手的概念错误，
地址为：https://github.com/itwanger/toBeBetterJavaer/blob/master/docs/src/sidebar/sanfene/network.md
具体如下：
错误描述：
文档中提到“服务器也及时回复了 SYN=2 和 ACK=1 的第二次握手”，这里存在对 SYN 字段的概念混淆，可能作者误写。
- TCP 中的
SYN是标志位（仅占 1 位），取值只能是0或1，表示是否为同步请求包；
正确逻辑：
服务器的第二次握手应是 SYN=1（表示同步请求）、ACK=1（表示确认）
附截图说明：
建议修改文档表述，以避免读者对 TCP 字段的概念产生混淆。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open docs/src/sidebar/sanfene/network.md and locate the explanation of why TCP uses a three-way handshake, specifically the wording about the server replying with SYN=2 and ACK=1. Correct the terminology so the second handshake describes SYN=1 and ACK=1, then review the surrounding explanation to ensure the TCP flag meanings are consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100