Last Modified: Mar 12, 2019
See more info
Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Opened: Jan 15, 2014
When ICC is applied to an html node and a client requests that html using the cookie header, if AAM serves the html from the cache, the operation inlines the content instead of referencing the content already present in the client's local storage. When the Lifetime interval for the html expires, AAM revalidates with the OWS (S10232) and replaces the links with references to the content in the client's local storage.
Content is inlined in the html even though it already exists in the clients local storage. When a client makes a request using the cookie header and AAM responds from the cache (S11101), AAM does not replace the links with references to the content in local storage.
ICC is enabled for node matching html.
Set Lifetime on the html pages to 0 to force each request to revalidate with OWS.