chrome上对wininet和winhtp的区别的说明

strikebone

于 2010-08-30 17:41:00 发布

阅读量655

点赞数

文章标签： chrome caching server cache api windows

本文探讨了WinHTTP和WinInet两个Windows网络编程接口的优缺点。WinHTTP拥有更清晰的API和支持，允许实现自定义缓存，但存在非ASCII URL编码和Keep-Alive连接的问题。相比之下，WinInet虽然API较为复杂且文档不全，但它经过了IE浏览器的长期实战验证。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Both come with all Windows versions we plan to support (Win2K and later).
WinHTTP is better documented. WinInet has a more difficult API and spotty documentation.
WinHTTP has a cleaner API with the support we need. A number of WinInet functions that are necessary for us (for example, for SSL state) are undocumented and unsupported, even though IE uses them.
WinHTTP allows us to implement our own cache. WinInet always shares a cache with IE. We would like to control our own caching, and also sharing a cache with IE can cause problems since some sites may serve browser-specific pages.
WinInet is better battle tested on account of being used by IE. WinHTTP is not used very much, and was designed for server use. It has problems with non-ASCII URL encodings sent by the server and keepalive connections. We have to provide workarounds for these issues.