FoxWeb does not currently support files that are this big. The problem is that the code attempts to read the whole POST data buffer in a VFP memory variable, which, as you can imagine can be problematic with data sizes exceeding 200 MB. In order to change this, we will have to enhance the Request object, so as to save the uploaded files to disk and pass the path to requested script.
We are planning to address this limitation in a future release, but for files this big you should also consider using a different upload mechanism, such as FTP.
Sent by Brent Lazerson on 03/01/2007 06:56:54 AM:
We are running VFP9, FoxWeb 3.5.1, and IIS 6 on a Windows 2003 Enterprise Edition Server. The hardware we are using is:
HP ProLiant DL 380 G4
Single Xeon 3.6Ghz Processor (Soon to be dual)
6GB of Ram
The problem we are having involves the upload of very large files to the server from client workstations. We are currently testing this on the LAN and when we hit transmit to upload the file from the workstation to the server the whole process times out after the 999 maximum script timeout set within FoxWeb.
These files are very large (>200mb) and while viewing the server statistics during the upload it shows the FWServer.exe process start to take up large amounts of memory and the processor spikes up to about 75 - 80% usage until the timeout. The file in it's entirety is transferred to the Foxweb\TempFiles directory but it never makes it to it's final destination and the process times out.
The exact error message we receive is:
The FoxWeb Service has returned the following message:
FoxWeb Timed Out--
Thanks in advance for any help you can provide.