0
250
ViewsASP.NET Core - Download .exe returns 404 error
I have a ASP.NET core MVC application and in the wwwroot folder, I've added another folder called "Shaun" and in that folder I've dropped an exe to try and download:
Now if I navigate to: http://localhost:PORT/Shaun/chromesetup.exe I get a 404 error. I've tried adding the Handler below but this doesn't work.
<add name="Client exe" path="*.exe" verb="*" modules="StaticFileModule" resourceType="File" />
Extra info: The reason I need to do this is because I have a client application that connects to this website, that client application is packaged using ClickOnce and gets dropped into the wwwroot of the website, this previously worked using MVC (pre Core) and still does, but doesn't with core.
How do I fix this?
2 answers
Answer question0
Try the following and tell me if it works:
app.UseStaticFiles(new StaticFileOptions
{
ServeUnknownFileTypes = true, //allow unkown file types also to be served
DefaultContentType = "Whatver you want eg: plain/text" //content type to returned if fileType is not known.
}
You can look at the sourcecode of StaticFileMiddleware to see how it handles static files.
On default the FileExtensionContentTypeProvider is used to check based on filename extensions what ContentType needs to be return in the Http Response headers. exe is not in this list.
So another option would be to add Exe to this list:
var provider = new FileExtensionContentTypeProvider();
provider.Mappings.Add(".exe", "application/vnd.microsoft.portable-executable"); //file ext, ContentType
app.UseStaticFiles(new StaticFileOptions
{
ContentTypeProvider = provider
});
0
In order for static files (.exe file is a static file type) to be served, you must configure the Middleware to add static files to the pipeline. The static file middleware can be configured by adding a dependency on the Microsoft.AspNetCore.StaticFiles package to your project and then calling the UseStaticFiles extension method from Startup.Configure:
public void Configure(IApplicationBuilder app)
{
app.UseStaticFiles();
}