Added Timeout for large files. Unfortunately .NET doesn't distinguish between read and write timeouts and assumes if there isn't a response it must have failed - despite the write queue being active. The assumption of setting this to Infinite is that the other end (Akamai Edge) will terminate the connection properly if it is sufficiently idle.

Author: colinbendell

NetStorage/NetstorageCMSv35Signer.cs

@@ -210,6 +210,11 @@ public Stream Execute(WebRequest request = null)
             {
                 //Disable the nastiness of Expect100Continue
                 ServicePointManager.Expect100Continue = false;
+                //Another hack to avoid problems with the read timeout even though the 
+                //bytes are being sent to the client. .NET doesn't distinguish between
+                //a read timeout and a writetimeout.
+                request.Timeout = System.Threading.Timeout.Infinite;
+
 
                 if (this.UploadStream == null)
                     request.ContentLength = 0;

NetStorageTest/HttpWebRequestTest.cs

@@ -49,6 +49,7 @@ public class HttpWebRequestTest : WebRequest
         public override string Method { get; set; }
         public override WebHeaderCollection Headers { get; set; }
         public override long ContentLength { get; set; }
+        public override int Timeout { get; set; }
 
         private Uri itemUri;
         public WebResponse NextResponse = null;