I added the following line in a call to myApp.config(): $httpProvider.defaults.headers.common['Cache-Control'] = 'max-age=0, must-revalidate';
This appears to have corrected it but a colleague is verifying. On Thursday, August 6, 2015 at 9:34:06 AM UTC-7, George Wilson wrote: > > Greetings all, > I have been looking around and am having a hard time finding a definitive > solution but we are having an issue with an AngularJS based Java > application deployed to WebLogic. Ideally, any files which are updated > following a new build would be updated and served to the browser. This > appears to be the case with all of our Javascript files (We are seeing 304 > responses for assets which have not been updated) but with our partial > templates this does not appear to be the case. Fiddler is showing those > assets as being served "from Cache". Ideally we would not have to > completely do away with caching but rather would only update cached files > if a change has occurred. > > Any ideas? > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
