[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! ]
Synopsis: directory names that end in backslash do not work State-Changed-From-To: feedback-closed State-Changed-By: pcs State-Changed-When: Sat Jan 30 11:31:04 PST 1999 State-Changed-Why: This is not a bug in Apache. First, when giving directories in the configuration file you should not end the directory with a slash (in either direction). Apache adds the slash itself when creating filenames from the configured directory names. Second, as the instructions say, use forward slashes as directory separators. Backslashes can have special meanings. In this case, a backslash at the end of the line means that the directive continues on the next line. This is why you got an error. The error is because the contents of the *next* line are being used as additional arguments to the current directive, hence the error message. So, remove the trailing backslash, and convert the backslashes into forward slashes.
