views:

468

answers:

4

I would like to handle requests differently depending upon the MIME type. For example, I have PDF's, images and other media files that I would like to prohibit access to based on their respective MIME types. Any ideas on how to do this? Thanks for the help.

I should also note that accessing the Windows registry is not an option for my application.

A: 

If I am understanding your question properly, you are serving static files and want to be able to do processing on a static file request in order to decide whether or not the user has access to that file. (based on MIME type)

If you map all files requests through a custom IHttpHandler (see the handlers section of your web.config file), you should be able to accomplish this.

In ProcessRequest (or BeginProcessRequest if you implement an asynchronous handler), you can call HttpContext.Current.Server.MapPath("~" + HttpContext.Current.Request.Path) (might be a better way to do that) to get the current static file being requested.

You can then analyze the extension of that file to make your decision.

Not sure if thats what you want, but hopefully it helps

LorenVS
That's very close to what I want, but I was hoping there was a more automatic way of doing it, rather than analyzing the extension. Something more along the lines of Request.MIMEType. Thank you for your input!
mkelley33
A: 

This information is in the registry, in HKEY_CLASSES_ROOT\<file_extension>\Content Type

using(var key = Registry.ClassesRoot.OpenSubKey(".htm"))
{
    string mimeType = key.GetValue("Content Type") as string;
}
Thomas Levesque
Thanks for the input, but the technical requirements I was handed dictate no registry access.
mkelley33
+1  A: 

.NET's mime-type mappings are stored in an internal class (System.Web.MimeMapping), so are not available to your code. The best you can do is steal the list, which you can get using Reflector and decompile the static constructor (cctor).

You're best off simply creating a list of supported extensions and their mime type and storing it on a dictionary. (The list inside MimeMapping is a tad verbose)

Richard Szalay
That's exactly the route I took. I'm sure I missed some extensions, but they would most likely be corner cases best dealt with as they arise to satisfy the "being productive/working software" requirement LOL. Thanks for the suggestion! I never knew about the MimeMappings. Very cool!
mkelley33
+3  A: 

I had a similar problem a few month ago and solved it with this simple wrapper-class around System.Web.MimeMapping (as mentioned by Richard Szalay):

/// <summary>
/// This class allows access to the internal MimeMapping-Class in System.Web
/// </summary>
class MimeMappingWrapper
{
    static MethodInfo getMimeMappingMethod;

    static MimeMappingWrapper() {
     // dirty trick - Assembly.LoadWIthPartialName has been depricated
     Assembly ass = Assembly.LoadWithPartialName("System.Web");
     Type t = ass.GetType("System.Web.MimeMapping");

     getMimeMappingMethod = t.GetMethod("GetMimeMapping", BindingFlags.Static | BindingFlags.NonPublic);
    }

    /// <summary>
    /// Returns a MIME type depending on the passed files extension
    /// </summary>
    /// <param name="fileName">File to get a MIME type for</param>
    /// <returns>MIME type according to the files extension</returns>
    public static string GetMimeMapping(string fileName) {
     return (string)getMimeMappingMethod.Invoke(null, new[] { fileName });
    }
}
J. Random Coder
Any problem with avoiding the dirty hack by referencing a public type? `Assembly.GetAssembly(typeof(System.Web.HttpApplication))`. As long as the method and referenced type don't change or disappear, that is... ?
Nelson
I like your variable name for Assembly.
aloneguid