View a List of Output Caching Rules (IIS 7)
Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista
To manage output cache rules easily, you can view a list that contains all output cache rules for a particular configuration level. You can sort this list by file name extension, action, or entry type. You can also group rules by entry type to see quickly which rules apply at the current configuration level and which rules are inherited from a parent level or you can group rules by action.
Prerequisites
For information about the levels at which you can perform this procedure, and the modules, handlers, and permissions that are required to perform this procedure, see Output Caching Feature Requirements (IIS 7).
Exceptions to feature requirements
- None
To view a list of output cache rules
You can perform this procedure using the user interface (UI) or a command line. For information about opening IIS Manager, see Open IIS Manager (IIS 7).
To use the UI
Open IIS Manager and navigate to the level you want to manage. For information about navigating to locations in the UI, see Navigation in IIS Manager (IIS 7).
In Features View, double-click Output Caching.
Command Line
To <do_something>, use the following syntax:
appcmd command object parameter:value | parameter:variable | parameter:option1 | option2
The variable <variable_name> is <description_of_variable>. For example, to <do_something_specific>, type the following at the command prompt, and then press ENTER:
appcmd <exact_command_to_accomplish_the_procedure>
Note
When you use Appcmd.exe to configure the <element_name> element at the global level in IIS 7, you must specify /commit:WEBROOT in the command so that configuration changes are made to the root Web.config file instead of ApplicationHost.config.
For more information about Appcmd.exe, see Appcmd.exe (IIS 7).
Configuration
The procedure in this topic affects the following configuration elements:
<caching>
For more information about IIS 7 configuration, see IIS 7.0: IIS Settings Schema on MSDN.