Webserver
Webserver
IIS Architecture
= Kernel (System Mode) – executing code has access to hardware
= User Mode – executing code has no access to hardware and memory (needs API to access
hardware)
IIS – a request processing architecture that includes
= WAS (Windows Process Activation Service) – enables to use protocols other than HTTP and
HTTPS
= Web server engine that can be customized by adding or removing modules
= Integrated request-process pipelines from IIS and ASP.NET
How IIS process http requests
= When a Client browser initiates http request, http.sys intercept this request
= validity check, if invalid, error code, otherwise ..
= Check if the request is in cache, if so, send the response right away, if not..
= Check if the request is static or dynamic
= HTTP.sys contacts WAS to obtain data from the configuration store (applicationHost.config)
= WWW Service receives the information
= WAS starts a worker process for the application pool
= worker process processes the request and returns a response to http.sys
= client receives the response.
Apache Architecture
Apache operation
=Two-phase operation: start up and operational
= Start up
= Read configurations, load modules and libraries
= Initialized required resources (log files, shared memory, database connection)
= Single process, single thread program and full system privileges
= Operational
= Normal operation by MPM
= Run as unprivileged user