03-14-2017 12:47 PM
Hi All,
is there a way to verify if on the second time when the data have been taking is from the WAAS cache?
thanks for answering
Solved! Go to Solution.
06-29-2017 07:02 PM
If you are referring to the HTTP Object Cache using AKC then the best option I have found to validate this is by reviewing the ce-access-errorlog in the errorlog directory of the branch WAE. Find the connection you are looking for in the log and if it was pulled from the local cache you should see a hit 'h' for your x-cache-status. The other option would be to enable debug headers which can be done by executing the following command on the branch WAE:
debug accelerator http object-cache response-headers
These headers will be viewable using the developer tools in your browser, and will allow you to verify that it was served from the local Akamai cache.
03-14-2017 01:06 PM
Hi Dawit,
There are several kinds of cache in WAAS, what kind of cache/traffic are you talking about ?
If you're talking about the DRE cache, you can check the DRE statistics on the "show stat connection conn-id <number>". But be aware that DRE cache is NOT session specific, the content is being reused and shared by several sessions.
Best regards
Finn
06-29-2017 07:02 PM
If you are referring to the HTTP Object Cache using AKC then the best option I have found to validate this is by reviewing the ce-access-errorlog in the errorlog directory of the branch WAE. Find the connection you are looking for in the log and if it was pulled from the local cache you should see a hit 'h' for your x-cache-status. The other option would be to enable debug headers which can be done by executing the following command on the branch WAE:
debug accelerator http object-cache response-headers
These headers will be viewable using the developer tools in your browser, and will allow you to verify that it was served from the local Akamai cache.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: