网络数据封装过程
关于网络数据如何通过Internet遍历的问题。
我想知道在通过Internet发送请求时,每个跳跃都会在每次跳跃中进行封装/除外过程。 (参考 https://afteracademy.com/例如,blog/what-is-data-data-and-de-de-de-in-networking )
例如,我从我的私人笔记本电脑发送http/s请求到 www.google.com 。 当Google Web服务器收到我的请求时,它会准备响应。我了解这些步骤如下。
- Google Web服务器将HTML数据放入HTTP(第7层)数据流中。
- 数据流将被封装到传输层(第4层)
- 等等。...(直到第1层)
当Google响应通过Internet穿越时,它传递了多个啤酒花(例如Internet服务提供商的路由器)
问题:每个跳跃是否会再次进行除圈(查找信息)和封装(以转发响应)过程? 例如,我希望路由器(第3层)将响应软件包删除到第3层,在该响应软件包中读取相关信息,然后再次将其封闭 - 因此,路由器不会一路解密到第7层?
提前致谢!
A question about how network data traverses through the internet.
I'm wondering whether the encapsulation/de-capsulation process happens at each hop while a request is being sent through the internet. (Reference https://afteracademy.com/blog/what-is-data-encapsulation-and-de-encapsulation-in-networking)
For example, I send a HTTP/S request from my private laptop to www.google.com.
When the Google web server receives my request, it prepares its response. I understand the steps are as follow.
- Google web server puts HTML data into a HTTP (layer 7) data stream.
- Data stream to be encapsulated into Transport layer (layer 4)
- and so on.... (until layer 1)
When the Google response traverses through the internet, it passes multiple hops (like routers from the Internet Service Provider)
Question: Does each hop conduct the de-capsulation (to lookup information) and encapsulation (to forward the response) process again?
e.g. I would expect a router (layer 3) to de-capsulate the response package up to layer 3, where it reads the relevant information, and capsulate it again - so the router wouldn't de-capsulate all the way to layer 7?
Thanks in advance!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
路由器仅在L2/L3下运行,它们查看数据包的目标IP地址。他们不在乎数据包有效载荷。每个跳跃将查找其路由表以将数据包转发到目标地址。
Routers only operate at L2/L3 and they look at the destination IP-address of the packet. They don't care about the packet payload. Each hop will look up its routing table to forward the packet to the destination address.