Received: (qmail 67874 invoked by uid 501); 11 May 2000 10:22:37 -0000 Message-Id: <20000511102237.67873.qmail@locus.apache.org> Date: 11 May 2000 10:22:37 -0000 From: Eric Maryniak Reply-To: e.maryniak@pobox.com To: submit@bugz.apache.org Subject: Minor documentation omission about DocumentRoot in httpd.conf X-Send-Pr-Version: 3.110 >Number: 6070 >Category: documentation >Synopsis: Minor documentation omission about DocumentRoot in httpd.conf >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Thu May 11 03:30:01 PDT 2000 >Closed-Date: Fri Sep 15 11:56:55 PDT 2000 >Last-Modified: Fri Sep 15 11:56:55 PDT 2000 >Originator: e.maryniak@pobox.com >Release: 1.3.9 >Organization: >Environment: SuSE Linux 6.3 >Description: The #commented docu about DocumentRoot in the 'default' httpd.conf describes DocumentRoot as: === # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. === This is not entirely accurate imho, because (at least on SuSE Linux 6.3) symlinks are _not_ followed by default, because of a: Options -FollowSymLinks ... ... >How-To-Repeat: N/A. >Fix: I would change the phrasing to: === # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory. # Symbolic links, unless disabled by a 'Options -FollowSymLinks', and # aliases may be used to point to other locations. === >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: slive State-Changed-When: Fri Sep 15 11:56:54 PDT 2000 State-Changed-Why: The basic apache distribution does allow symlinks in the document root, so SuSE must be modifying their configuration without changing the comments. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]