I have a daily routine that generates a new airgap reponse file which I have been using for a few years now. Recently the size of the airgap response file greatly increased and I am not sure what might have changed. I find is I run the routine manually I also get a large file size. Noth has changed on my side, same sitefile list same version of the airgap tool 9.5.15, so I am thining maybe something has changed on the HCL side of the coin.
Below is a screenshot of what I am seeing, as you can see the change in the file size is quite large.
We’d probably need a list of the sites you’re gathering to comment more meaningfully; but I note that’s about the time we released some major updates including BigFix 10.0.2, major updates to WebUI sites, changes in Mac content to handle OS renames, and changes in several sites to update non-Flash dashboards.
Hello, so stopping the gather of all the WebUI sites resulted in a airgap response file that was significantly smaller. 370 MB as opposed to 1.3 GB. What the heck is in the response file for the webui sites that makes it so large and does one need to gather those sites every day or just when changes to those sites are announced?
I believe WebUI pushes a lot of their app updates through site content.
If you are using the “normal” Airgap method where your server creates a request file, you should only be gathering delta updates. If you are using the “no-request” method where you manually list the sites to gather, you’ll get the full site echo time.
