>Number: 2849 >Category: mod_jserv >Synopsis: Inconsistent handling of path delimiters in Windows >Confidential: no >Severity: serious >Priority: medium >Responsible: jserv >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Aug 13 13:20:00 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.1 >Environment: NT4 SP3, JServ 1.0b from around the first week of August. >Description: JServ doesn't handle slash and backslash path delimiters consistently. Apache config file says to use forward slashes, e.g., for the JServLogFile. Using forward slashes writes the correct log file from the C code (I think it's the C code) of the module, but writes a file to an incorrect location from the Java code. For instance,
JServLogFile d:/applications/apache/logs/jserv.log creates two files, one in d:/applications/apache/logs/jserv.log and another d:/applicationsapachelogsjserv.log. Both files end up containing only part of the full jserv log. There are related problems in the jserv.properties file. Here, the wrapper.classpath parameters must use backslash path delimiters, while the other paths, such as the paths to the zone property files, must use forward slashes. >How-To-Repeat: Configure apache jserv on an NT box. >Fix: Accept forward slashes for all paths for consistency with Apache config files. Also accept backslashes for consistency with Windows conventions. Paths should be translated to whatever internal form Java is expecting (probably backslash delimited). >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
