Home


6.4 When not cache

When creating your high-level caching strategy, you first need to determine what pages in your store should be cached. Pages that are good candidates for caching are pages that are accessed frequently, but are also stable for a period of time, and contain content that can be reused by a variety of users. You should beware of caching security information and cookies.


Personalized fragments

Any servlet and JSP file content that is private, requires authentication, or uses SSL should not be cached externally. The authentication required for those servlet or JSP file fragments cannot be performed on the external cache.


Cookies and attributes

By default, dynamic caching caches the cookies (when caching by servlet class) and all request attributes (servlet and JSP pages) along with the cache entries. However, WebSphere Commerce cookies and request attributes contain user-specific information that should not be cached. As a result, the following property names and values are mandatory when caching full pages:

<property name="save-attributes">false</property>
<property name="store-cookies">false</property>

+

Search Tips   |   Advanced Search