Is there a recommended way to return an image using ASP.NET Web API

What is the best way to return an image with 2 parameters (x and y for resize).

For example

~/api/image12345/200/200

Will return a 200 by 200 jpg/png/or gif

Should I return a System.Drawing.Image object or manually define the HTTPReponseMessage.Content?

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

You shouldn’t return a System.Drawing.Image, unless you also add a formatter which knows how to convert that into the appropriate bytes doesn’t serialize itself as the image bytes as you’d expect.

One possible solution is to return an HttpResponseMessage with the image stored in its content (as shown below). Remember that if you want the URL you showed in the question, you’d need a route that maps the {imageName}, {width} and {height} parameters.

public HttpResponseMessage Get(string imageName, int width, int height)
{
    Image img = GetImage(imageName, width, height);
    using(MemoryStream ms = new MemoryStream())
    {
        img.Save(ms, System.Drawing.Imaging.ImageFormat.Png);

        HttpResponseMessage result = new HttpResponseMessage(HttpStatusCode.OK);
        result.Content = new ByteArrayContent(ms.ToArray());
        result.Content.Headers.ContentType = new MediaTypeHeaderValue("image/png");

        return result;
    }
}

But again, if you are doing this in many places, going the formatter route may be the “recommended” way. As almost everything in programming, the answer will depend on your scenario.

Method 2

Images are heavy. ASP.NET WebForms, HttpHandlers, MVC, and Web API all do a absolutely terrible job of serving static files. IIS does an extremely good job of that – Often 20-100x more efficiently.

If you want to get good performance, do URL rewriting at the latest during PostAuthorizeRequest, so IIS can pick up and serve the file. Yes, this means HttpModule-level event handling.
[Disclaimer: I’m the author of the following article and open-source project]
If you’re doing something dynamic with images, check out this article on image processing pitfalls to avoid, and consider taking a look at ImageResizer. It has excellent disk caching (which uses IIS static file handling), and is easy to connect to image generation of any kind. It has optional bindings for AForge, FreeImage, and WIC as well, if you need to get advanced.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0