Redirect fake extension requests that don't have a querystring #8

nathanaeljones opened this Issue Jul 17, 2012 · 1 comment


None yet

1 participant


IIS6 and Classic Pipeline users often use the .ashx fake extension to enable resizing:

I.e, image.jpg.ashx?width=100

However, if the querystring is dropped, the request 404s because ImaegResizer isn't handling it.

image.jpg.ashx -> 404.

A more user-friendly behavior would be to 301 redirect to image.jpg in this situation. However, this should only happen if there are NO querystring values, since a typo would result in redirect frustration.


Rewriting would offer a path to circumvent other middleware filters, such as the UrlAuthorizationModule. Classic pipeline usage persists, but is not as prevalent.

Usage in integrated mode often happens due to conflicts with CMSes or other middleware for the standard static file extensions. Usage is unlikely to decline significantly.

@nathanaeljones nathanaeljones modified the milestone: V4, V4 preview May 4, 2015
@nathanaeljones nathanaeljones added a commit that referenced 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.
@nathanaeljones nathanaeljones removed the ready label May 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment