Tag: technology

YES

NO

YES Limited by Hardware capacity

In theory there is no limit but creating more then 60 App Pools is not recommended.

IIS cannot save such settings. It will throw error.

Yes, This is perfectly acceptable and IIS will work accordingly.

No If you set the idle timeout for an application pool to a period of time that is longer than the time specified for time-based recycling, IIS will ignore the settings that you specify and instead use the default settings

YES, If you set the idle timeout for an application pool to a period of time that is longer than the time specified for time-based recycling, IIS will apply the longer time period settings.

YES

NO

NO, But can be programmed to do so.

YES but not FTP Users

In Process Memory

Hard disk

RAM

With in IIS processes

You can use an Fire wall to hide

You can use an http Handler to hide

You can use an ISAPI filter to hide

You can never hide.

wpw3.exe

wpwc.exe

http.sys

ISAPI.exe

Virtual directory cannot be renamed once created

by directly editing the Metabase.xml file

by directly editing the Metabase.config file

by directly editing the IIS Config file

To list worker processes that are currently running

To list Application pools to the worker process

To List application currenly running in each worker process

All of the above

The overhead for IIS to check a host header is very high compared to the total cost of satisfying an HTTP request, even for a static file

The overhead for IIS to check a host header is negligible compared to the total cost of satisfying an HTTP request, even for a static file

The overhead for IIS to check a host header is considerably high compared to the total cost of satisfying an HTTP request, even for a static file

None of these

Denial of service attacks

Degraded on service attacks

No such thing in IIS Vocabulary

None of these