If the upload is successful, a FileResult object is sent back to the client. Public override void OnActionExecuted(HttpActionExecutedContext actionExecutedContext)

Throw new HttpResponseException(HttpStatusCode.UnsupportedMediaType) Public override void OnActionExecuting(HttpActionContext actionContext) Public class ValidateMimeMultipartContentFilter : ActionFilterAttribute This can then be used for all uploads methods. The server method uses a ValidateMimeMultipartContentFilter attribute to check if the correct MIME type is sent. Names = (entry => ),ĬontentTypes = (entry => ),ĭescription = streamProvider.FormData,ĭownloadLink = 'TODO, will implement when file is persisited' Var streamProvider = new MultipartFormDataStreamProvider(ServerUploadFolder) Īwait (streamProvider) įileNames = (entry => entry.LocalFileName), Private static readonly string ServerUploadFolder = 'C:\Temp' //Path.GetTempPath() Public class FileUploadController : ApiController Namespace WebAPIDocumentationHelp.Controllers This server method works for both single and multiple file uploads. The headers are not always set depending on the client. The file(s) information is collected from the form data and the file headers. This saves the content to a provider location and creates a new file name with no endings. The Web API controller implements the server method for file upload. Links to other examples are also included at the bottom of this post.

The controller implementation saves the files in memory first, so for large files or with a lot of HTTP traffic, this is not a good solution. The examples use the MultipartFormDataStreamProvider class. This article demonstrates file uploads using Web API 2.

Mvc multiple file upload example