是否有使用 ASP.NET Web API 返回图像的推荐方法

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.

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.