Jonas Lindau
Oct 22, 2013
  3274
(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
Optimizely Opal: How to Build Effective Workflow Agents

If you're building workflow agents in Optimizely Opal, this post covers how specialized agents pass context to each other, why keeping agents small...

Andre | May 20, 2026

ReviewPR: An Azure Function That Reviews Your Azure DevOps Pull Requests With Claude

A while back I wrote about an  Azure Function App for PDF creation that we use to offload PDF rendering from our Optimizely DXP site. That same...

KennyG | May 19, 2026

Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 2 of 2)

The Real Transformation in Optimizely CMS 13: Why the Upgrade Itself Is the Easy Part. A field-tested playbook for enterprise teams moving from...

Hung Le Hoang | May 18, 2026

Is the most powerful AI model really the best value?

Artificial Intelligence is already becoming part of everyday software development. Developers now use AI tools to generate code, write documentatio...

K Khan | May 16, 2026