http连接复用
我想更好地了解 .Net http 连接重用是如何工作的。
当我使用 HttpWebRequest 从同一应用程序域向某个服务器发送两次内容时，连接（可选）是否被重用？因此，服务器会将两个请求视为来自同一连接，即使在我的应用程序中它们是不同的逻辑请求。
如果是，可以关闭此行为吗？
使用身份验证/ssl 的连接怎么样 - 它们是否也被重用？如果我为每个请求提供不同的凭据/策略，这可能是一个安全漏洞。
I would like to better understand how .Net http connection reuse works.
When I use HttpWebRequest to send something to some server twice from the same appdomain, is the connection (optionally) reused? So the server would see both requests as coming from the same connection even though in my application they are different logical requests.
If yes, can this behavior be turned off?
What about connections that use authentication/ssl - are they also also reused? If I supply different credentials/policy for each request this can be a security hole.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
连接重用使用 HTTP Keep-alive，这是 HTTP/1.1 的一项功能。通过使用 HTTP Keep-alive，一个 TCP 连接可用于按顺序处理多个 HTTP 请求，因此可以节省为每个请求打开新 TCP 连接的时间。每个 HTTP 请求本身又是独立的，因此身份验证和类似内容不会自动重复使用。
The connection re-use is using HTTP Keep-alive which is a feature of HTTP/1.1. By using HTTP Keep-alive one TCP connection is used for handling multiple HTTP requests sequentially so one saves time to open a new TCP connection for every request. Each HTTP request itself is then again independent so authentification and similar won't be re-used automatically.
正如 https://www.rfc-editor.org/ 中的 RFC 所说rfc/rfc2616#section-8.1
HTTP 标头：
连接：Keep-Alive
是 Http 1.0 使用的东西，因为连接不是持久的。
从 http 1.1 开始，默认情况下所有连接都是持久的，这意味着不再使用此标头。
As it says the RFC in https://www.rfc-editor.org/rfc/rfc2616#section-8.1
The HTTP header:
Connection: Keep-Alive
is something used by Http 1.0, because connection weren't persistent.
as of http 1.1 all connections are persistent by default, which means that this header is not used anymore.