================================================================================ FOXWEB -- The WWW-FoxPro Interface ================================================================================ Version: 3.6 You can always download the newest version and view up-to-date documentation at the FoxWeb WWW Site: http://www.foxweb.com Technical Support: FoxWeb Forum (http://www.foxweb.com) FoxWeb is distributed by: Eon Technologies 1226 Lincoln Ave. Alameda, CA 94501 USA E-mail: sales@eontech.com ================================================================================ INSTALLATION ================================================================================ 1. Log into Windows with administrative rights. 2. Make sure you have VFP and the WWW server software installed properly. 3. Close and uninstall older versions of FoxWeb (prior to 3.0) -- restart if necessary. 4. Run the setup program and follow the directions on the screen. 5. Run the FoxWeb Control Center to configure FoxWeb. 6. Open the FoxWeb documentation from the Start menu and continue with the Getting Started topic. ================================================================================ NOTES ================================================================================ 1. Switching to a different version of VFP: In order to switch to a different version of VFP you will need to run the FoxWeb setup program from the Add or Remove Programs applet in the Windows Control Panel. Select the Switch VFP Version option and pick the desired version from the list. Important: If you change to a different version of VFP, it is very important that you recompile ALL your scripts. FXP files that were compiled with a different version of VFP may still function, but in most cases behave erratically. 2. Temporary files: Each time the Channel Monitor kills unresponsive channels, 1 or more temporary files are left in the temp directory. These files should periodically be deleted to free disk space. 3. Upgrading from a previous version: You may not run FoxWeb 3 alongside previous versions on the same computer. If you wish to revert back to your old version, you will have to uninstall FoxWeb 3 and reinstall that version. Note that licenses for previous versions of FoxWeb are not valid for version 3. ================================================================================ REVISION HISTORY ================================================================================ Version 3.6 (1/3/2008) - BUG: Fixed bug that caused authentication cookies to expire on 12/31/2007, preventing Auth.SaveCookie from functioning properly. - BUG: Fixed issue that prevented the value of the Response.Charset property from being sent to the client. - BUG: Fixed minor bugs in show_channels2 diagnostic script. - BUG: Can now call show_channels2 directly from a browser. - FEATURE: Response.Clear does not only clear the output buffer, but also clears any unsent HTTP headers, such as the status, cookies and the content- type. Version 3.51 (9/26/2006) - BUG: "Cannot find library" error when running FoxWeb Control Center without the VFP 9 run-time DLLs. - BUG: Empty line separating HTTP headers, causing the last few to be visible in the HTML content. Version 3.5 (9/21/2006) - BUG: HTTP headers are now separated with CRLF instead of just LF, so as to comply with RFC 822 and 2616. - BUG: Sets SAFETY to OFF at the beginning of each request to prevent channels from hanging. - BUG: Channels were continuously restarting when running in a Terminal Services or Remote Desktop session. - bug: Fixed "Variable 'ADDLTIME' not found" error in show_channels2.fwx. Version 3.3 (3/2/2006) - FEATURE: Response.Write is no longer limited by VFP's maximum string size and as a result does not require that output is split in smaller chunks. - FEATURE: Added show_channels2.fwx diagnostic tool. - BUG: Changed to a non-sequential algorithm for generating session IDs to prevent "guessing" of other IDs issued by the server. - BUG: FoxWeb Control Center would not operate if error log table was locked by another instance of VFP. - BUG: Error 11 "Function argument value, type, or count is invalid" on servers with multiple GB of memory (caused by SYS(3050, 1) returning a negative number). - BUG: Invalid subscript reference error in cases where multipart data is not received in its entirety from the browser (FoxWeb can only find one instance of the multipart boundary string). - BUG: Unable to enter 4-digit values for Buffer Memory Size in the FoxWeb Control Center. Version 3.1 (5/15/2005) - FEATURE: Added support for VFP 9. - FEATURE: Modified auth object so that it "waits" .3 seconds after an incorrect login to prevent brute force attacks. - FEATURE: Added Auth.AcknowledgeUserID property. - FEATURE: Web based error viewer supports exporting into XML format (for tech. support purposes). - BUG: Calling FWStart and FWStart /close from a Terminal Services window fails to start/stop the FoxWeb service. - BUG: Start/Stop button in FoxWeb Control Center does not work properly if running in a Terminal Services window. - BUG: Session table gets corrupted when channel gets killed if stored on remote share -- even if no script is executing script execution. Added FLUSH command to mitigate this problem. - BUG: "202 Invalid path or filename -513" error when temp. folder does not exist. Session object now checks whether Temp. Directory exists and returns an error message if it does not. - BUG: Client ip address not being included in Session.Token. - BUG: Cookie-less sessions would not work for channels with 2-digit numbers. Version 3.0 (12/15/2004)