Share via

Add a cache profile

  • Article

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2016-11-14

Before you perform this procedure, confirm that:

Important

At the minimum, you must be a member of the Site Administrators SharePoint group to complete this procedure.

Add a cache profile

Use this procedure to add a cache profile.

To add a cache profile

  1. On the Home page of the site collection, on the Site Actions menu, point to Site Settings, and then click Modify All Site Settings.

  2. Under Site Collection Administration, click Site collection cache profiles.

  3. On the Cache Profiles page, click New.

  4. In the Title section, type a title for the cache profile.

  5. In the Display Name section, type a name for the cache profile.

    The display name appears in the list of available cache profiles for site owners and page layout owners.

  6. In the Display Description section, type a description for the purpose of the cache profile.

  7. In the Perform ACL Check section, select the check box to ensure that all items in the cache are security trimmed.

    Although you can clear the check box to provide additional speed, you should only do this for sites or page layouts that do not have information that needs to be security trimmed. By default, the Perform ACL Check box is not checked.

  8. In the Enabled section, select the check box to enable caching.

    If this check box is cleared, no caching will take place in any location where this profile is selected.

  9. In the Duration section, type the number of seconds that the cached version will be available.

    Note

    The default duration for the out-of-box cache profiles (Public Internet, Extranet and Intranet) is 180 seconds. When creating a new cache profile, consider the maximum length of time you want a page to be in the cache, keeping in mind that site users will potentially see stale content during that time.

  10. In the Check for Changes section, select the check box to validate on each page request that the site has not changed and will flush the cache on changes to the site.

    Although you can clear the check box to enhance performance, when you do this, the system does not check for updates to the site for the number of seconds specified in the Duration section. This can result in users not getting the most current information.

  11. In the Vary by Custom Parameter section, type the custom parameter as specified by HttpCachePolicy.SetVaryByCustom in ASP .NET 2.0. For more information, see HttpCachePolicy.SetVaryByCustom Method (https://go.microsoft.com/fwlink/?LinkId=121544&clcid=0x409).

  12. In the Vary by HTTP Header section, type the custom parameter as specified by HttpCachePolicy.VaryByHeaders in ASP .NET 2.0. For more information, see HttpCachePolicy.VaryByHeaders Property (https://go.microsoft.com/fwlink/?LinkId=121545&clcid=0x409).

  13. In the Vary by Query String Parameters section, type the query parameter as specified by HttpCachePolicy.VaryByParams in ASP .NET 2.0. For more information, see HttpCachePolicy.VaryByParams Property (https://go.microsoft.com/fwlink/?LinkId=121546&clcid=0x409).

  14. In the Vary by User Rights section, select the check box to ensure that users must have identical effective permissions on all securable objects to see the same cached page as any other user.

  15. In the Cacheability section, select the cache type as specified by HttpCacheability in ASP .NET 2.0. For information, see HttpCacheability Enumeration (https://go.microsoft.com/fwlink/?LinkId=121547&clcid=0x409).

  16. In the Safe for Authenticated Use section, select the check box for the policies that you want to allow administrators and page layout designers to apply to authenticated scenarios.

  17. In the Allow writers to view cached content section, select the check box to bypass the normal behavior in which people with edit permissions have their pages cached.

    Enable this behavior in scenarios in which you know that the page will be published, but will not have content that might be checked out or exist in draft form, such as a Content Query Web Part.

  18. Click OK.

Additional references

Output Caching and Cache Profiles