|
The following issues are fixed in this release kit. (* indicates fixes that are new since the last WS251x general release patch file.)
Up to 50 "require group" and "require user" lines are now allowed for each directory entry in the ACCESS.CFG file (or for each ACCESS.WWW file). You can also put more than one entry on each line (separating each with a space) up to a maximum line length of 255 characters.
Web Manager will automatically put more than one user or group on a "require user" or "require group" line.
Web Manager will now add a user's full context name to the "require user" line, allowing for users from multiple contexts to be specified even if they have the same user names but reside in different contexts.
When entering a user name when the browser asks for a username and password to access a restricted document, only the user name has to be entered. The authenticating user does not need to enter the full context when authenticating as long as the user name specified in the access control file has the full context.
The number of "allow" lines in a directory entry in the ACCESS.CFG file (or in each ACCESS.WWW file) has been increased to 50.
Aliases to users now works properly when "require group" is used to establish access control.
A long URL (greater than about 450 characters) will no longer cause the file server to abend.
Access and Error log files now roll properly as configured through the Web Manager utility.
The Web Server will no longer abend if the same page is accessed many times.
Having an extra '_' character in a volume name will no longer cause problems accessing ~user home pages.
The Web Server will process more than one thread at a time.
The Netscape Navigator browser will no longer return "Document contains no data" errors if the document was last downloaded by an Internet Explorer browser.
Text file based user and group authentication has been corrected.
The Web Server will now automatically close TCPIP connections that are being left open. The default wait time is 5 seconds, but it can be modified by setting the TCPLinger Time in the HTTPD.CFG file. However, if the TCPLinger Time is set in the HTTPD.CFG file and Web Manager is subsequently run, the Web Manager utility may delete that entry when it re-writes the HTTPD.CFG.
The access log file will no longer contain a '?' in a log file entry unless the URL passed to the server specifically contains it.
The NDS browser will no longer return a -603 error when browsing an organization role.
The NDS browser will no longer return an error when browsing an organization role that contains a slash in the name.
Accessing Perl scripts in rapid succession no longer causes a memory leak of its small memory allocations.
A Perl script containing an infinite loop will no longer hang the server.
Perl support for long file names was added.
Additional library directory paths can be specified within Perl.
PERLGLOB.NLM now unloads itself automatically when it completes it's processing.
Web Manager no longer greys out the names of users in the parent directory after "All valid users" was clicked in a child directory.
In Web Manager, the extra separator bar below the Copy menu item has been removed.
If when running Web Manager you are authenticated to two trees, and your default tree is NOT the same tree the Web Server is installed in, you will be prompted to change trees. This is to eliminate the wrong NDS information showing up in Web Manager.
The Homepage and Photo NDS object attributes can now be added to other NDS objects besides the user objects.
When using a NetWare Administration utility that supports long file names (such as NWADMIN95.EXE) you can now specify a long file name for the homepage of an object in the NDS tree.
* Volume names containing more than one underscore (_) would not be parsed correctly. This caused various problems such as a user's home directory not being found.
* Document contains no data errors when a document is accessed by Internet Explorer, then immediately accessed by Netscape Navigator.
* The HTTP.NLM would only use one of the threads it allocates when it starts up, even if simultaneous requests are received.
* HTTP.NLM not rolling access and error logs properly.
* HTTP.NLM abends due to the server passing an invalid semaphore number to THREADS.NLM.
* Abends when accessing the same Web page many times.
* File based (as opposed to NDS based) user and group authentication problems.
* TCPIP connections climbing and not being released. By default, old connections are not automatically removed and, if an ACK is never returned by the client to the server the connection may remain open indefinately. A new directive has been added. To set the timeout to automatically remove lingering TCPIP connections, add "TCPLingerTime sec" to the HTTPD.CFG file and reload HTTP.NLM (where 'sec' is the number of seconds before the connection is removed).
* A slash (/) in an object name causing NDS browsing errors.
* The question mark (?) in the access log file causing problems with third-party log file analysis tools.
* A user logging in with a username that is a substring of another user's name and with a password which is a substring of the other user's password could access the web page as that other user.
* The ACCESS.CFG directive "order allow, deny" would cause HTTP.NLM load time errors because of the space between "allow," and "deny".
* PERL5 has been added, allowing multi-threaded Perl requests. Perl 5 also runs as an LCGI application, eliminating any security risks from an intruder connecting to an RCGI port.
|
