Troubleshoot and support > Cache > Dynamic caching in an application


Troubleshoot: Cacheable objects cannot be created or invalidated due to encrypted URL parameters

When parameters and the values in a Web address are encrypted, the WebSphere Commerce dynamic caching mechanism cannot use them to form, or to invalidate, cache entries. If you are encrypting those parameters, you need to modify the wc-server.xml file, to specify the parameters that you do not want encrypted. This is the standard way to resolve encrypted parameter related problems for caching.

For example, to specify that the storeID and langID parameters are not to be encrypted, you can add the following <NonEncryptedParameters> tag after the <ProtectedParameters> in the wc-server.xml file as shown in the following example:

  ...
 
<ProtectedParameters>
     ...
 
</ProtectedParameters>
  
<NonEncryptedParameters>
    
<Parameter name="storeId"/>
    
<Parameter name="langId"/>
  
</NonEncryptedParameters>
   ...


+

Search Tips   |   Advanced Search