Yesterday, I picked up on an old code piece of mine - sending images to the client via an HttpHandler. Why in the world would you implement that with a handler when there is http.sys kernel mode caching? Well, I had a few unique constraints:
Now, a common approach to sending images from a certain directory (leaving requirement #2 by the wayside for the moment) would be this:
image.aspx?image=iamthebest.jpg
So what is wrong with this approach? First and foremost using an ASP.NET page. The page lifecycle is a drain on performance and throughput, because you simply don't need it. That sorts out why I chose to go with an HTTP handler.
Secondly, somebody could DOS your server. You heard me right. For the background, check the article Trap Alert: Files that aren't. A .NET version (managed C++) of this checker can be found in this download (the article Dateityp-Ermittlung in Managed C++ is only available in German).
How do you get around this issue? Well, how about reading the directory up front, and instead of having the filename in the URL, send the hash! When the image is requested, take the hash and look up the corresponding file, presto. In addition you get one security feature for free: no directory traversals can be hidden in your code.
When I uncovered the code yesterday, I decided to rewrite it for more general use. So what do you get?
Usage of ImageCache is demonstrated in default.aspx.cs plus the source code of default.aspx (design time of the control does not work, known issue).
The code behind looks like this (CreateMapping loads the directory contents, initializes the hash to file name map, stores it into the cache):
using ChrisOnNET.ImageCache;public partial class _Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { // normally, this would be done in global.asax ImageCache.CreateMapping("demo", Server.MapPath("~/TestImages/")); // the DIY approach to rendering the image tag string testHash = ImageCache.GetHashForFile("026.jpg", "demo"); Response.Write("<image src=\"Image.ashx?bucket=" + "demo" + "&image=" + Server.UrlEncode(testHash) + "\" />"); // the elegant approach to rendering the image tag Response.Write("<image src=\"" + ImageCache.GenerateUrl("036.jpg", "demo") + "\" />"); // see HTML source for server control approach (Design time not working, known issue) }}
Rendering Image tags in Page_Load isn't nice, but after all it is only intended to show the functionality. Most likely you are going to use the declarative ImageCacheControl anyways:
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %><%@ Register Assembly="ImageCacheControls" Namespace="ChrisOnNET.ImageCache" TagPrefix="cc1" %>
<html xmlns="http://www.w3.org/1999/xhtml" ><head runat="server"> <title>Untitled Page</title></head><body> <form id="form1" runat="server"> <div> <br />Using the ImageCacheControl: <cc1:ImageCacheControl ID="ImageCacheControl1" Bucket="demo" FileName="026.jpg" runat="server" /> </div> </form></body></html>
That's basically it. Let me know what you think.
ImageCacheTakeOne.zip (59.55 KB)