Owin UseStaticFiles not respecting RequestPath

Question

**EDIT: NOTE: This appears to be fixed in later versions of the Owin StaticFiles middleware, so if you have this probem, simply upgrade **

My OWIN configuration has this:-

   string root = AppDomain.CurrentDomain.BaseDirectory;
   var staticFilesOptions = new StaticFileOptions();
   staticFilesOptions.RequestPath = new PathString("/foo");
   staticFilesOptions.FileSystem = new PhysicalFileSystem(Path.Combine(root, "web"));
   app.UseStaticFiles(staticFilesOptions);

When I hit /foo/app/app.js I get a 404 error, when I hit /web/app/app.js the file is returned.

How is RequestPath meant to work in conjunction with PhysicalFileSystem?

You could try the OWIN Framework implementation of StaticFiles which I am sure does not have this problem. — bikeman868, Jan 15 '17 at 06:19

score 10 · Answer 1 · answered Jul 08 '14 at 17:09

10

I tested this code snippet and it works for me from this sample project.

app.UseFileServer(new FileServerOptions()
{
    RequestPath = new PathString("/foo"),
    FileSystem = new PhysicalFileSystem(@".\web"),
});

Make sure you have this in your web.config:

<system.webServer>
    ...
    <modules runAllManagedModulesForAllRequests="true"></modules>
    ...
</system.webServer>

answered Jul 08 '14 at 17:09

Ben Wilde

5,552
2
39
36

Yup, this appears to be fixed in the latest OWIN nuget packages. – Ian Mercer Jul 08 '14 at 18:16
@IanMercer, I'm using version 2.1.0, the latest stable release, which came out last January. – Ben Wilde Jul 08 '14 at 18:37

score 1 · Answer 2 · answered Feb 28 '18 at 02:02

I got the same problem. Acording to the answer of @Rafael here. Add the following configuration to Web.config then it resolves my issue:

<system.webServer>
<handlers>
  <remove name="StaticFile"/>
  <add name="Owin" verb="" path="*" type="Microsoft.Owin.Host.SystemWeb.OwinHttpHandler, Microsoft.Owin.Host.SystemWeb"/>
</handlers>
</system.webServer>

Hope this help the other people!

score 0 · Answer 3 · answered Mar 18 '14 at 13:28

RequestPath you define a virtual path for your static resources used in requests, see this as a route to your static files.

Using PhysicalFileSystem you define the path for the static file lookup.

So, if there is a request for what you've defined in RequestPath the path-part is translated to the directory on your harddisk.

In your case you should receive the status code of 404 for web/app.js (as this is your directory and not your route) and a 200 for foo/app.js.

"Should" but that's not happening. Did you try it? – Ian Mercer Jun 30 '14 at 04:08 — Ian Mercer, Jun 30 '14 at 04:08

Owin UseStaticFiles not respecting RequestPath

3 Answers3

Linked