Timeouts usually are not an issue for the server, but **the client**. Clients are the ones that typically time out a connection if it takes to long.

Is this in a browser or with an HTTP Client? If the latter you should be able to control the timeout time.

Also, IIS has request limits that are set in various places. These values are frustrating to set because there are several of them - one for IIS, one for ASP.NET and sometimes it's not always clear which one is the problem because some AsP.NET operations (or other framework) defer to IIS for things like file downloads for example.

As to actual response size can be set with this:

<security>
    <requestFiltering>
        <requestLimits maxAllowedContentLength="5024000000" />
    </requestFiltering>
</security>

As to response timeout on the server (in seconds):

<system.web>
    <httpRuntime executionTimeout="180" />
</system.web>

Pretty sure though that that timeout is pretty long by defaut that you should never hit that. I've certainly never run into an issue with that.

+++ Rick ---

>Hi All
>
>I have a VFP app which downloads a ZIP file using a call to a HTTP URL. I also have a WinDev app calling the same URL. A client has poor internet connection. If the ZIP file is largish then it downloads for a while and then suddenly fails to download anymore. My suspicion is that this is a timeout issue on the server i.e. if the file takes too long to download then the server drops it. I am note sure where to investigate this timeout setting on the server running IIS8 Windows 2012 R2. The time before the file stops downloading varies a bit but I suspect it is around a few minutes (3 or so, maybe 5?).
>
>Any suggestions?
>
>Thanks.