dvilner

We have several sites that run PHP content on IIS6 (PHP version 5.3.3); "404" handling is configured as default (404b.html). My question is: how is "404" really handled? For instance, if a request for a missing PHP file comes through, does the IIS intercept, sending a 404 back to the client, or the request get handled by the PHP processor FIRST and then it's handed off to the IIS? Thank you!

Running PHP 5.3.3 on IIS6 (Win 2K3) in a load-balanced farm; the content (.php files) is served from a UNC share (IIS is configured to "connect as" domain\serviceAccount to authenticate) . Every time a request for a PHP file is made, there are two processes spawned: php-cgi.exe running as domain\serviceAccount and the 2nd php-cgi.exe, running as "NETWORK SERVICE". The problem is high CPU utilization on the servers... Does anyone know if this is by design or something is misconfigured? Thanks in advance!