Web acceleration include list - what will it include?
LTM 11.5.4 here. I would like to setup a web acceleration profile for multiple sites that use the same Virtual. For right now I ONLY want to cache the home page. Let's say the home page for this site is /welcome. If I put /welcome in the URI include list, will it cache all elements (images, css, etc.) found on /welcome, or only the HTML response of /welcome? I tried putting in .jpg and it turned it into (?glob).jpg. Using jpg as an example, should I be putting in "*.jpg" or just ".jpg" in the include box? Would I need to put trailing backslashes (/welcome, or /welcome/ or both?). Finally, if I ONLY put certain elements in the include list (I deleted the default ".*" in the include list box which will allow caching on everything), is it safe to assume that these are the only items that will be cached?334Views0likes3CommentsCaching occurring, even though Web Accel profile was removed from VS?
Env: LTM 11.5.2 plain, no hotfixes Hmm. We have a virtual server that, when originally setup, had a optimized_caching web acceleration profile associated with it. But in early testing (over a year ago), the caching was noted to cause problems, so I removed the web acceleration profile from the VS config. However, now, over a year later, the app team has rolled out a new version on their app servers - and pieces/parts of that application are acting as if the old version is in place. The original (no longer used) web acceleration profile still exists - but when I listed ramcache objects on it, there are none. Nevertheless, just for grins, I deleted it ... and the app started working better. Not 100% ... but clearly better. Is there any record of a defect that would relate to this? I.e., a web acceleration profile that was removed from a VS still impacting that VS? Or, alternatively, can anyone think of any other explanation of how deleting the vestigial profile could have any impact? Truth in lending disclosure here -- the app is still not 100%. It improved markedly, but there are still issues. Thoughts?264Views0likes2Comments