On a couple of client sites, enabling the Azure CDN Toolkit in the web.config resulted in the site not loading at all and eventually timing out. On closer inspection this was due to the use of non-existent crop names in the views on the sites. Adding a null check as per this pull request fixed the issue and meant that the sites loaded correctly.
Jeavon
commented
6 years ago
On a couple of client sites, enabling the Azure CDN Toolkit in the web.config resulted in the site not loading at all and eventually timing out. On closer inspection this was due to the use of non-existent crop names in the views on the sites. Adding a null check as per this pull request fixed the issue and meant that the sites loaded correctly.