Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Falling through to IIS now requires opt-in #54

Open
Tratcher opened this issue Aug 11, 2015 · 0 comments
Open

Falling through to IIS now requires opt-in #54

Tratcher opened this issue Aug 11, 2015 · 0 comments

Comments

@Tratcher
Copy link
Member

A change has been made to the IIS ASP.NET 5 server (Microsoft.AspNet.Server.IIS) such that applications must opt into IIS fallback. Previously when a request reached the end of the managed pipeline without being handled it would automatically unwind the managed pipeline and fall back to IIS. Now the end of the managed pipeline will return an empty 404 response like on other servers. To opt into the fall-through use the new extension app.RunIISPipeline(); at the end of your managed pipeline. This extension will no-op on non-IIS servers.

The primary impact is for static files. Before there was significant confusion on if requests were being handled by the managed static file ASP.NET middleware or the native static file IIS module. Now IIS will not try to serve static files without the opt-in extension. Alternatively applications can use the app.UseStaticFiles() or app.UseFileServer() extensions to use the managed static file middleware.

See aspnet/Hosting#323 for discussion.

@Tratcher Tratcher added this to the 1.0.0-beta7 milestone Aug 11, 2015
@aspnet aspnet locked and limited conversation to collaborators Aug 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant