An error occurred while saving the commentSam Stephens commented
The thing is that there are situations where image requests need to hook into the infrastructure of a website. For example usage for a project I've been involved in requires the images being resized to be secured based on user roles and metadata associated with the image record. For this project, it makes sense to route these requests via an MVC controller so the authorisation approach and code is standardised across both views and images.
So, whilst usage of ActionResult may indicate naivety, there are legitimate reasons to deal with image requests via MVC controllers.
Honestly I think that if you wish to discourage use of ActionResult, you need to make the HttpModule approach easier, rather than make ActionResult harder to use and disadvantage those of us who have legitimate reasons for using it.Sam Stephens supported this idea ·