A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Jonas Lindau
Oct 22, 2013
  3091
(0 votes)

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.
Latest blogs
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025