config/8939: Apache configuration bug or bug in documentation

[Vladimir Terziev <vl...@rila.bg>]

>Number:         8939
>Category:       config
>Synopsis:       Apache configuration bug or bug in documentation
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Dec 04 09:10:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     vlady@rila.bg
>Release:        1.3.12 and 1.3.22
>Organization:
apache
>Environment:
OS: FreeBSD 4.3-STABLE
Compiler: GCC
Apache: 1.3.12 and 1.3.22
>Description:
Apache documentation says, that the context of SetEnv configuration directive is
server config and virtual host. This means that .htaccess files are out of the
scope of SetEnv context.
The problem (may be the bug - I'm not sure) in configuration is that I use
SetEnv in .htaccess files and it works perfectly!
I discover that SetEnv is controlled by FileInfo subdirective in AllowOverride
directive. This is only a fact, not a bug.
I think there is a bug in apache documentation, but if I'm wrong, it means that
there is a bug i Apache config.
>How-To-Repeat:
You can write a CGI script, which prints the content of environment viriable,
created in .htaccess file.
>Fix:
Just fix the apache documentation.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> 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!     ]