1. caching to the disk is controlled by browser, not by flex/flash. The browser cache can be saved to the disk, flash player cache will only be in the memory.
2. By default, browsers can cache content over http ( if you didn’t set no-store no-cache in the header ).
3. However, browsers may not cache content to disk over https by default and you need to configure it.
For IE, you can turn on the feature by change setting at:
Tools > Internet Options > Advanced tab > Security section > Do not save encrypted pages to disk
For Firefox, see details in
4. Only signed RSLs can be stored in the player cache, unsigned will be in browser cache. Only Adobe can create signed RSLs. If you create an RSL that contains a customer library, it will be unsigned, so can’t be in player cache. There is no workaround for this at the moment. Your option is to use unsigned with browser’s cache.
5. If your app get an connect problem over the first request, but works fine after a refresh, that usually is caused by the content cache over https issue. See above for how to correct it.
February 2016 M T W T F S S « Oct 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29