The default memory pool size for the http client cache is 10 Mb. The recommended cache pool size depends on the available system memory and the user’s applications. Frequently used files should be cached to improve performance. So the user should total up the sizes of
most commonly used application files and media files to come up with his desired cache pool size. Any URL data that cannot be fitted into the available memory in the cache will not be cached. Configuring a zero (0) value for the http client cache memory pool effectively turns off the caching feature.
Configuring a portion of the router memory as a cache pool for the http client does not mean that amount of memory is immediately set aside exclusively for the http client. The http client grows its cache memory pool on an as-needed basis. It allocates memory along the way as more and more http URLs are fetched into the router.
Oh, well there you go! Man, that is a lot of prompts.
I have no guidance from Cisco, but I would be uncomfortable with assigning more than 100MB of your present RAM to the cache. If you increased the memory of the router to 1GB, I would be comfortable assigning all the extra memory to the cache.
I think you need the manufacturer's guidance on this one.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...