From ad715e95df67857d94c669fe09047ca0c59f6182 Mon Sep 17 00:00:00 2001 From: John Reilly Date: Sat, 26 Dec 2015 15:52:05 +0000 Subject: [PATCH] Update static-files.rst Fix typo in filename --- aspnet/fundamentals/static-files.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/fundamentals/static-files.rst b/aspnet/fundamentals/static-files.rst index 9211385954..eae7bad560 100644 --- a/aspnet/fundamentals/static-files.rst +++ b/aspnet/fundamentals/static-files.rst @@ -154,7 +154,7 @@ To specify a different default file from the ones listed above, instantiate a `` app.UseStaticFiles(); ... -Now, if the user browses to a directory in the webroot with a file named ``mydefault.htm``, that file will be served as though the user typed in the fully qualified URI. +Now, if the user browses to a directory in the webroot with a file named ``mydefault.html``, that file will be served as though the user typed in the fully qualified URI. But, what if you want to serve a default page from a directory that is outside the webroot directory? You could call both the ``UseStaticFiles`` and ``UseDefaultFiles`` methods passing in identical values for each method's parameters. However, it's much more convenient and recommended to call the ``UseFileServer`` method, which is covered in the next section.