You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.The text was updated successfully, but these errors were encountered: