You should be able to set the CacheControlCustom property in IIS for a particular directory, whether the proxies honour it or not is another story.
An alternative is to work around the problem from the client side. If you can reproduce the problem (eg it is your ISA server causing the problem ;-) then try accessing one of the offending xaps via your browser. eg: www.yourdomain.com/clientbin/module1.xap You would expect to get the cached version. Then hit ctrl-F5 on the same URL and if you get the correct version, you then know that might be able to work around it by setting the following headers in your webrequest : Cache-Control: no-cache Pragma: no-cache Watch the headers in Fiddler to see what the browser does when you tell it to bypass the cache by hitting ctrl-F5 I don't know if all proxies will honour that either. Of course I am assuming you have control over the webrequest that is fetching your additional modules. On Thu, Jun 10, 2010 at 4:31 PM, noonie <[email protected]> wrote: > Stephen, > > You could enable Content Expiration on the folders that contain the > resources. > > The problem is that some Proxy Servers are configured to ignore what you > want :-( > > -- > Regards, > noonie > > On 10 June 2010 16:24, Stephen Price <[email protected]> wrote: >> >> but all of the modules have old content. > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > _______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
