ProGet times out serving 10MB package over slow link

We're seeing issues where NuGet clients are timing out on a GET of a normal-sized package (10MB) from a ProGet feed. This only happens when the download is happening across a slow WAN link. For local clients with decent connectivity to the service we've never seen it occur.

Packet captures show that the package is streamed by the service for 120 seconds after which time no additional TCP segments are sent (the NuGet client has acknowledged all TCP segments). Our WAN link is spotty so this is typically enough to transfer 6-8MB of the package but not the entire payload. No additional data is streamed after this point. At 420 seconds the NuGet client closes the connection with an error message.

The Windows event log shows the following:

Event code: 3001 
Event message: The request has been aborted. 
Event time: 10/3/2014 9:35:43 AM 
Event time (UTC): 10/3/2014 1:35:43 PM 
Event ID: 06cb782e5408437cb9e0e464814e8b3e 
Event sequence: 14 
Event occurrence: 2 
Event detail code: 0 
 
Application information: 
    Application domain: e906d479-1-130568155811533752 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\Program Files\ProGet\WebApp\ 
    Machine name: XXXXXXXX
 
Process information: 
    Process ID: 2824 
    Process name: ProGet.Service.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 
 
Exception information: 
    Exception type: HttpException 
    Exception message: Request timed out.

 
 
Request information: 
    Request URL: http://XXXXXXXXXX:81/api/v2/package/Client/Desktop.Client.Setup/0.0.1602 
    Request path: /api/v2/package/Client/Desktop.Client.Setup/0.0.1602 
    User host address: 10.5.32.44 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
 
Thread information: 
    Thread ID: 81 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Is impersonating: False 
    Stack trace: 
 
 
Custom event details:

Product: ProGet
Version: 3.1.7

In this case, it may be best to switch to IIS as the web server to host ProGet. The integrated server is meant more for simplicity and getting started more quickly, and isn't as robust when dealing with these types of network issues.

The instructions to do so are here: http://inedo.com/support/kb/1013/hosting-buildmaster-or-proget-through-iis-instead-of-the-integrated-web-server