https://bz.apache.org/bugzilla/show_bug.cgi?id=70094

            Bug ID: 70094
           Summary: RewriteCond Directive: Environment variables confused
                    with server variables (“Most are documented in […] the
                    Environment Variables doc”)
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: All
               URL: https://httpd.apache.org/docs/trunk/en/mod/mod_rewrite
                    .html#rewritecond
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: Documentation
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

The RewriteCond Directive section of the mod_rewrite reference documents which
forms its first argument takes and mentions server variables in an unordered
list of 4 items. The explanation of server variables contains:
> These variables all correspond to the similarly named HTTP MIME-headers, C 
> variables of the Apache HTTP Server or struct tm fields of the Unix system. 
> Most are documented in the Expressions doc, in the Environment Variables doc, 
> or the CGI specification (RFC 3875).
This confuses environment variables with server variables. As
https://httpd.apache.org/docs/trunk/en/env.html#url-rewriting explains:
> The %{ENV:variable} form of TestString in the RewriteCond allows 
> mod_rewrite's rewrite engine to make decisions conditional on environment 
> variables. Note that the variables accessible in mod_rewrite without the ENV: 
> prefix are not actually environment variables. Rather, they are variables 
> special to mod_rewrite which cannot be accessed from other modules.
> 
By the way, “struct tm fields of the Unix system” is not particularly clear.

🅭🄍: https://www.philippecloutier.com/Common+infrastructure+licensing#its

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to