HTTP. sys

Strictly speaking, HTTP. sys is no longer in the scope of IIS, so HTTP. sys configuration information is not stored in the metabase of IIS, but is defined in the registry. The path of the HTTP. sys registry entry is hkeylocal machine/systemlcurrentcontrolsetlservices/HTTP 0 HTTP. sys, which brings the following benefits.

? Continuous monitoring: As HTTP. sys is a network driver and is always running, it can respond to users' HTTP requests in a timely manner.

? Better stability: http. sys runs in the operating system kernel mode and does not execute any user code. Therefore, HTTP. sys is not affected by web applications, working processes, and IIS processes.

? Data cache in kernel mode: If a resource is frequently requested, HTTP. sys caches the response content, and the cached content can directly respond to subsequent requests. Because this is a cache based on the kernel mode, there is no switch between the kernel mode and the user mode, and the response speed will be greatly improved.