Error 404 on images/files when running EPiServer CMS 6.0 on ASP.NET 4.0

I found this excellent post regarding ASP.NET 4.0 and EPiServer CMS 6:

http://world.episerver.com/Articles/Items/EPiServer-CMS-60-now-supporting-ASPNET-40/

I followed all steps and, surprise: No images, no working downloads… hmm… Luckily, it turned out to be a simple fix! The site had some handlers registered for certain file types, and they had a runtime-version specified this way:

   1: <add name="*.jpg_GET,HEAD" path="*.jpg" verb="GET,HEAD"

   2: type="EPiServer.Web.StaticFileHandler, EPiServer"

   3: preCondition="integratedMode,runtimeVersionv2.0"/>

Just remove the attribute preCondition and it works fine!

Oct 22, 2013

Comments

Please login to comment.

Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

See all blogs