Usually EPiServer CMS UI only reload the whole page when it is needed. That is when you change context to another page, block, media or a another version.
If you turn on EPiServers Content Caching it should not add any browser cache headers for content where WorkID>0. Actually it sets cachability to private and expires to yesterday in this case so nothing should be cached in your browser.
It would be intresting to see the http response headers for the request fetching the preview of the page (without you turning of caching in developer tools). For this to work you probably have to clear the cache first.
My guess it that other configuration or code is adding cache headers to these requests.
True that the first thing is not my problem.
I totally agree that the problem seems to be that something else are setting the cache header but I cannot find out what.
The strange thing is that it does not always happen, right now I cannot reproduce it anymore.
I recored a video showing the problem that I send to support, if you want I can mail it to you if you would like to see the problem
I think I have found it. We were setting the response header Last-Modified to the time the page was saved and because of that the request to the page send the parameter If-Modified-Since and it seems like there is a miss in time there.
I have no removed the manually setting of Last-Modified and cant right now reproduce the error.
In one site I am upgrading to the latest version of EPiServer I suddenly start to have problem with pages not beeing updated.
After some investigation I saw that the problem seem to be on when the site thinks it should load from client cache and not inside onpage edit mode. If I activate developer toolbar and tell it to never use cache I am not able to reproduce the problem.
I thought the in edit mode it should never use cache but it seem to do that.
Have anyone else also seen this?