This content has been marked as final. Show 3 replies
Im pretty sure you need to make any cache changes on the server via administration or server side script. You can however fool it by adding a random parameter to the url request that the browser ignores and the xml file cant use like url?randomgarbage=19873098732jhdskh983yqehdp that will fool it, however your best bet would be to use an HTTPService for that and bypass the problem completely.
I realized I could add the cache-buster metatags to the HTML wrapper, and that seems to have done the trick.
<META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
<META HTTP-EQUIV="EXPIRES" CONTENT="Sat, 01 Jan 2000 00:00:01 GMT">
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
However... I'm interested in learning more about "using an HTTPService" to "bypass the problem completely". Everything I read suggested that URLLoader was the way to go for loading my local XML. How would HTTPService solve the problem?
I was not aware you were loading your xml locally, If you are indeed pulling the data off the same client the app is running on then you can embed the xml directly in the app.
<mx:XML id="myData" source="myData.xml" />