Request timeout from ASP.NET Core app on IIS

Question

I make a web request to a third-party api from my ASP.NET Core application.

When app is running alone itself, request succeeds.
When app is running in IIS on the same server, request timeouts.

Request is made from a Hangfire recurring job to Asana API endpoint (HTTPS) via RestSharp client. All the own app's pages are available through IIS, but app cannot make any requests.

Where should I look and what to debug to solve this problem?

If you're just trying to change the request timeout on IIS, then you can look here: stackoverflow.com/a/38507709/5656858 — Stout01
– Stout01, Commented Mar 29, 2017 at 15:55
@Mikhail Zhuravlev Just out of interest: how did you solve the problem? — The incredible Jan
– The incredible Jan, Commented Mar 9, 2023 at 10:51

Daboul · Accepted Answer · 2017-03-29 15:55:40Z

19

IIS behavior is driven by the web.config, I have configured to deal with request < 20 min specifying requestTimeout="00:20:00":

<aspNetCore
  requestTimeout="00:20:00"
  processPath="%LAUNCHER_PATH%"
  arguments="%LAUNCHER_ARGS%"
  stdoutLogEnabled="false"
  stdoutLogFile=".\logs\stdout"
  forwardWindowsAuthToken="false">
  <environmentVariables>
    <environmentVariable name="ASPNETCORE_ENVIRONMENT" value="staging" /> <!-- value could be "development", "staging" or "production"-->
  </environmentVariables>
</aspNetCore>

answered Mar 29, 2017 at 15:55

Daboul

2,8131 gold badge21 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

Mikhail Zhuravlev Over a year ago

Doesn't it set timeout for requests that come into IIS? Because my problem is related to requests that come from the app to another app on anoter server with a RestSharp client. And when app is running without IIS, those requests are passing ok.

Daboul Over a year ago

My bad, I didn't get you right then. But what does trigger the call from your ASP.NET Core, an incoming call to IIS right? What about your application if your incoming call from IIS timeout? Wouldn't your app and its request get interrupted as well? Not sure about that, just a supposition.

Mikhail Zhuravlev Over a year ago

No, there is no incoming request, it's a recurring job set with Hangfire.

ElFik Over a year ago

Is it possible to specify requestTimeout as an environment variable ala %LAUNCHER_PATH%? When I attempt this, intellisense indicates The string '%REQUEST_TIMEOUT%' is not a valid Time value. and my navigating to my webapp gives: The specified CGI application encountered an error and the server terminated the process.

SO19 Over a year ago

@Daboul - This is good information but this setting is not applied. Reason with details is - I read the details for these settings on this page - learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/… & it turned out that default hostingModel setting is InProcess & requestTimeout setting for this hosting model is ignored. Here is snap from that page "Doesn't apply to in-process hosting. For in-process hosting, the module waits for the app to process the request." Please let me know about this.

|

Collectives™ on Stack Overflow

Request timeout from ASP.NET Core app on IIS

1 Answer 1

8 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

8 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related