Episerver - update 361

When an AccessDeniedException is thrown and a handler handles the necessary redirect, we don't explicitly set cache headers that forces no caching of the response.

Today we only set 'private' which should stop proxies from caching the response, but we can be even more explicit and set both 'no-store' and 'no-cache'.

DefaultContentUrlCache is using IObjectInstanceCache and not ISynchronizedObjectInstanceCache. Therefore, URLs are not removed from all instances in a load-balanced setup.

Reported from Content url caching not invalidating on synchronized sites (episerver.com)

How to reproduce:

• Set up a load-balance environment with remote events.
• Upload an asset.
• Render link to asset in a view.
• Access the view from both nodes and click the link.
• Change the URL to the asset from one of the nodes.
• Refresh the view on the other node and click the link.

Steps to reproduce:

1. Create and publish a configurable view that allows editors to create Editional blocks (that is, blocks having TinyMCE). 
2. Open the view on CM.
3. Add new > Enter required field. 
4. Enter data to Mainbody (TinyMCE property)
5. Click Save.

Actual result:

Error script : widgets.js:2 Uncaught TypeError: Cannot read property 'tagName' of null
at Object.set (widgets.js:2)
at Object._onChange (widgets.js:2)
at Object.<anonymous> (widgets.js:2)
at widgets.js:2

Expected result:

No error script.

This is an issue where during an indexing job, the number of documents increases as expected on the Overview page. But when the job finishes, the number of indexed documents are significally reduced again.