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

RequestTimeout in ASP.NET Core 3.1 is not availablewhen using InProcess Hosting #23160

Closed
chrismcmorran opened this issue Jun 19, 2020 · 1 comment
Labels
area-runtime Includes: Azure, Caching, Hosting, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions ✔️ Resolution: By Design Resolved because the behavior in this issue is the intended design. servers-iis Includes: IIS, ANCM Status: Resolved

Comments

@chrismcmorran
Copy link

Describe the bug

When hosting in process on IIS the httpRuntime requestTimeout attribute is ignored. The documentation states that the module will wait for the app to finish processing the request. I am currently migrating a project from .NET Framework to ASP.NET Core 3.1; I don't believe that there is any way to limit the amount of time that a request will be processed before being stopped by the runtime. Is this functionality available via middleware? Hosting out of process is not an option and I would like to avoid using a thread to track execution time.

@javiercn javiercn added area-runtime Includes: Azure, Caching, Hosting, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions servers-iis Includes: IIS, ANCM labels Jun 19, 2020
@BrennanConroy
Copy link
Member

httpRuntime has the executionTimeout setting, and ANCM has the requestTimeout option.

requestTimeout is not supported with in-process https://docs.microsoft.com/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1#in-process-hosting-model.

We would suggest writing custom middleware for request timeouts.

@BrennanConroy BrennanConroy added the ✔️ Resolution: By Design Resolved because the behavior in this issue is the intended design. label Jun 22, 2020
@msftbot msftbot bot locked as resolved and limited conversation to collaborators Jul 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-runtime Includes: Azure, Caching, Hosting, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions ✔️ Resolution: By Design Resolved because the behavior in this issue is the intended design. servers-iis Includes: IIS, ANCM Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants