Windows httpd V1.4c Release Notes

Release date: 09-Jun-94

Please monitor the Server's New Home Page

This is the Version 1.4c production release of Windows httpd (formerly NCSA httpd for Windows). This software was written by Bob Denny <rdenny@netcom.com>. Please note: This software is no longer "freeware". See the Software License Agreement.

Windows NT and Windows 95

Windows httpd does not run under Windows NT or Windows 95. The direct CPU and stack bashing I did to achieve the fast multithreading under 16-bit Windows is not compatible with NT and 95. I am also the author of the O'Reilly WebSite server, part of a commercial web publishing package for Windows NT and Windows 95. For more info on WebSite see WebSite Central.

WinSock Bugs

Field tests have revealed weaknesses in some of the Windows Sockets packages that are in common use. My network I/O routines make use of features that were put into WinSock to permit concurrent transactions, and to minimize the impact of communications on the rest of the system. Also, httpd is a server, and therefore uses connection functions that are different from those used by client programs.

I have done quite a bit of work in diagnosing WinSock/TCP problems with several WinSock packages. I have passed my findings along to the authors/developers of these packages. If you are interested in my findings, see Windows HTTPD and TCP: A Report for more information. If you experience communication hangs, incomplete document deliveries, etc., try adding "-n" to the httpd command line. This disables multi-session support, disables all Windows efficiency optimizations, and reverts to simple blocking-mode operation. If this "cures" your problem, you need to gather evidence for submitting a bug report to your WinSock vendor.

Remove the "-n" and enable the network I/O tracing feature of httpd and look at the log. I will be glad to assist in interpretation. If it turns out to be a server bug, I'll fix it. If not, you'll have to live with single-session support and lower performance (with "-n turned on) until you can get your WinSock package fixed.

CGI Scripting

There are severe limitations with using COMMAND.COM as the shell for executing CGI scripts (see the DOS Scripting docs). In addition, I have discovered that there is a limit to the number of DOS virtual machines that can be exec'ed before Windows will crash. This means that your system has a limited life if you use DOS-based scripts.

If you have Visual Basic, I strongly recommend that you take advantage of the Windows CGI interface. All of the CGI-required data items, plus fully decoded Mosaic forms fields, are made available by the interface. Samples, including a CGI test "script" are included with the package, in the cgi-src directory. The file CGI.BAS contains a description of the interface, plus all of the code to handle setting up the CGI environment within Visual Basic. It is also possible to use other Windows programming environments such as Access or FoxPro, but you'll need to get familiar with the environment using Visual Basic first.

Support

The author is not in a position to provide commercial-grade technical support for this server. I will specifically not become involved with hardware, Windows memory management, or network software setup issues. Direct your questions and problems to the comp.infosystems.www.providers USENET newsgroup. I monitor this newsgroup, as do many other people who may be able to help you with questions and/or problems. Server configuration and operation has been kept as similar as possible to the Unix httpd.

Also, please monitor the New Windows httpd server home page for news, updates, and contributed packages, scripts, etc.


Features supported:


Changes since V1.4

Changes since V1.3

Return to the Overview
Robert B. Denny <rdenny@netcom.com>