title: ASP.NET request timeout after 90 seconds - Service Unavailable 503
body: <p>My web application (ASP.NET 4.0) makes a call to a server from client-side (using AjaxPro library, but I don’t think it makes any difference). The call is starting a potentially long-running task on the server – sometimes it may tike about 5 minutes to complete. I’m more than happy to wait this time but for some reason my request gets interrupted after exactly 90 seconds – 2 m 60 seconds (according to FireBug). 
  It sends back Service Unavailable 503 message. This happens only when I host my application on IIS (7.0), it works without problems (i.e. processes the request for all 5 minutes without interrupting it) on my local PC in debug mode from VS2010 on ASP.NET Development Server. </p>
  
  <p>I have tried several things so far:</p>
  
  <ul>
  <li>I increased AjaxPro global timeout: AjaxPro.timeoutPeriod = 1000000;</li>
  <li><p>I modified my web.config file like follows:</p>
  
  <p>&lt;httpRuntime maxRequestLength="102400" executionTimeout="360" /&gt;
  &lt;sessionState timeout="60"&gt;&lt;/sessionState&gt;</p></li>
  <li><p>In IIS Manager -> Sites -> My website -> Advanced Settings I increased value of Connection Time-out (seconds) property. </p></li>
  </ul>
  
  <p><img src="https://i.stack.imgur.com/6TpTu.png" alt="enter image description here"></p>
  
  <ul>
  <li>In the application’s application pool -> Advanced Settings I increased all possible timeouts: </li>
  </ul>
  
  <p><img src="https://i.stack.imgur.com/B2LF3.png" alt="enter image description here"></p>
  
  <ul>
  <li>I tried to increase HttpContext.Current.Server.ScriptTimeout in the server side handler's code.</li>
  </ul>
  
  <p>Noting seemed to help. It works fine on ASP.NET Development server but when it comes to IIS it just cuts off my requests precisely after 90 seconds.</p>
  
  <p>Any thoughts, guys? </p>