![]() Therefore, if a 60 MB file might take 24 minutes via FTP, it will take 48+ minutes using the ASP.NET upload.Īny ideas as to why this is so slow? Any thoughts on options out there? We do not want to have them using an FTP program like WSFTP due to security reasons. Using WSFTP, the file came across in 2 minutes and 10 seconds. Under straight HTTP, it took 4 minutesĪnd 2 seconds. Under SSL, it took 4 minutes and 6 seconds. I just ran a couple of tests on a 5 MB file. The site is under SSL due to the content being for the government, but I do not believe that this is effecting it. ![]() From the Manual: 'By default, NeatUpload does not directly limit the size of uploads. Therefore, if the POST fails (due to its size), it cannot fire the page's events. Actually, even the small files are taking a long time. 404 and missing PageLoad: IIS can only process the request once the complete POST is on the server. I have tinkered with some different httpRuntime parameters and am able to successfully upload these files, however, they are taking an extremely long time. Video and some of the newer files are anywhere from 20 MB to 60+MB. When this was designed, it was just PDFs and they were at most 4 MB. I have built a small ASP.NET app that allows a client to upload different files for their clients.
0 Comments
Leave a Reply. |