03-21-2018, 05:50 PM
For further clarification, here is some info on HTTP.Sys (from https://www.mikeplate.com/2011/11/06/sto...n-windows/)
First of all, the way http.sys works on newer Windows versions is a very useful feature. The reason behind http.sys is to have a single system service that listens on the all-important port 80 and be a mediator to different applications and services in the system that might like to handle incoming requests on port 80 but for different urls. What an integrated Windows application does, is use a Windows API for registering its own urls and then have them directed to itself. At the same time, there can be other applications also getting incoming requests to port 80 but for different registered urls.
So I am wondering if there is a way make intraweb register itself with HTTP.SYS and only register a certain URL, instead of blocking the entire port 80.
First of all, the way http.sys works on newer Windows versions is a very useful feature. The reason behind http.sys is to have a single system service that listens on the all-important port 80 and be a mediator to different applications and services in the system that might like to handle incoming requests on port 80 but for different urls. What an integrated Windows application does, is use a Windows API for registering its own urls and then have them directed to itself. At the same time, there can be other applications also getting incoming requests to port 80 but for different registered urls.
So I am wondering if there is a way make intraweb register itself with HTTP.SYS and only register a certain URL, instead of blocking the entire port 80.