The application|iis| program |application|iis recently debugged an ISAPI extension that needs to know the identity of processes and threads. The knowledge that is learned.
MSDN Original: IIS application identities.
ISAPI extensions (including ASP, ASP.net, because both Asp.dll and Aspnet_isapi.dll are ISAPI extensions):
The identity of the process (Process,w3wp.exe):
1. In anonymous access mode, use IUSR_computer_name account.
2. Non-anonymous way to use the identity of a certified customer.
The identity of Threads (thread):
1. Win32 RevertToSelf has not been invoked, as is the process identity.
2. Win32 RevertToSelf was invoked, and in IIS6 worker process isolation mode, the thread disguised as an "NT authority\network SERVICE" account. (thread impersonates the NT authority\network SERVICE account).
In fact, this account can be set in "Application Pools".
If you create a new thread (_beginthread ()) in your thread, the new thread runs under the NT authority\network SERVICE account.
In IIS6, each website and virtual directory can be individually set application settings to a separate application Pool. Each application Pool is in a separate w3wp.exe process.
