Re: config/3000: BrowserMatch(NoCase)/SetEnvIf(NoCase) allowed in htaccess

[co...@apache.org]

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> 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: BrowserMatch(NoCase)/SetEnvIf(NoCase) allowed in htaccess

Release-Changed-From-To: 1.3.x-1.3.1
Release-Changed-By: coar
Release-Changed-When: Sun Sep 13 21:20:20 PDT 1998
Category-Changed-From-To: pending-config
Category-Changed-By: coar
Category-Changed-When: Sun Sep 13 21:20:20 PDT 1998

Re: config/3000: BrowserMatch(NoCase)/SetEnvIf(NoCase) allowed in htaccess

[Randy Jae Weinstein <rw...@is7.nyu.edu>]

With the new 'IfDefine' directive, it would be great if we could allow in
the .htaccess file items like:

SetEnvIf HTTP_USER_AGENT "^Mozilla/[0-3]" Netscape
<IfDefine !Netscape>
 # Set non-netscape stuff here.
</IfDefine>

Yet another advantage to allow SetEnvIf in .htaccess.  This also calls for
a change in IfDefine. Currently, IfDefine's parameter-name argument is a
define as given on the httpd command line via -Dparameter-, at the time
the server was started. Would be better to allow it to also use the
attributes from SetEnv.

-Cheers,
 RJW