UseWelcomePage is too greedy

[richlander]

Experience:

• Create empty ASP.NET vNext project in VS
• Add text file to project
• Launch site
• Type URL for text file
• Server returns file. Yeahh!
• Add app.UseWelcomePage()
• Type URL for text file
• Server does not return file. Bad.
• Add app.UseStaticFiles();
• Type URL for text file
• Server returns file. Yeahh.

The text file should still be returned in the case that startup.cs only includes app.UserWelcomePage().

[Praburaj]

The text file was served in the first place without app.UseStaticFiles() is because IIS staticfile module handled the request. This does not work when you move out of IIS and use WebListener/Kestrel. So registering static files middleware is necessary for a reliable/predictable static file behavior.

[richlander]

I didn't move out of IIS in this scenario, however. The environment was IIS throughout.

[Tratcher]

UseWelcomePage takes an optional argument to specify the path it should listen on (exact match). However, the default is wildcard/any. Maybe the default should be "/", the current root.

Side note, this issue should be moved to the Diagnostics repo.

[Tratcher]

This issue was moved to aspnet/Diagnostics#51