StaticFileHandler no longer assigned when VirtualPathProvider has existing file #140

Closed
nathanaeljones opened this Issue May 12, 2015 · 0 comments

Projects

None yet

1 participant

@nathanaeljones
Member

In .NET 4.0, simply exposing a resource via a StaticFileHandler does not enable it to be served. This undocumented change causes 'unmodified' files from being retrieved via an ImageResizer provider.

The workaround is to specify StaticFileHandler for those requests, a la

<system.webServer>
<handlers>
  <add name="StaticGifImages" path="*.gif" verb="*" type="System.Web.StaticFileHandler" />
  <add name="StaticPngImages" path="*.png" verb="*" type="System.Web.StaticFileHandler" />
  <add name="StaticJpgImages" path="*.jpg" verb="*" type="System.Web.StaticFileHandler" />
</handlers>
</system.webServer>
@nathanaeljones nathanaeljones added a commit that closed this issue May 12, 2015
@nathanaeljones nathanaeljones Major core changes: Assign StaticFileHandler for all VPP-only request…
…s (Fixes #140). Apply .Rewrite changes to all (existing) image requests (fixes fake extension issue #8 and #113). Call ImageMissing for *all* image 404, not just those processed.
1e397ae
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment