Jonas Lindau
Oct 22, 2013
  3276
(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
Understanding Optimizely Opal Cost

Opal pricing are transparent at large extent, It is based on a credit consumption model rather than fixed per-user licensing or tokens consumptions...

K Khan | May 25, 2026

Optimizely CMS 12 Now Fully Supports .NET 10

This is the latest installment in our ongoing series covering .NET version support for Optimizely products. If you've been following along, you may...

Bien Nguyen | May 25, 2026

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