Developer forum

Hi Melissa

I am not sure there is a solid reasoning behind the current default. We have seen a number of sites that excutes all kinds of weird stuff on e.g. customer receipt pages or in custom apis and those would timeout due to this setting.

For most frontend requests, this setting should be maybe 5-10 seconds max.

I believe you can modify web.config something like this - adding a low timeout per default and increase it for specific paths or handlers (This is .net 4, DW9.)

<configuration>
  <system.web>
    <!-- Short default for everything -->
    <httpRuntime executionTimeout="60" />
  </system.web>

  <!-- Long-runner gets more time -->
  <location path="taskhandler.ashx">
    <system.web>
      <httpRuntime executionTimeout="1800" />
    </system.web>
  </location>
</configuration>

These kind of configurations are very dependent on the actual implementation - so there is really not a very good default that covers majority of scenarios.

BR Nicolai