DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19711>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19711 SetEnvIf and SetEnvIf do not work under Windows 2000 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2003-05-10 02:59 ------- Andre, thanks so much for all the help. Your successful test helped point me in the right direction. Turns out it was related to Mod_SSL. After extensive testing and reconfiguration, here is a summary of the final solution: 1. When using Mod_SSL, CustomLog entries in apache.log do not get processed. 2. To resolve this issue, the CustomLog entries have to be placed in the ssl.conf file. 3. My CustomLog configuration in ssl.conf then became: SetEnvIfNoCase Request_URI "^/tsweb/$" mylogvar CustomLog logs/mylog.log common env=mylogvar It would be nice if the developers could find some way of resolving this so that CustomLog entries in apache.conf do not get ignored when using Mod_SSL. However, since there is a workaround, I will now mark this bug report as WORKSFORME - unless someone feels a more elegant resolution is warranted from the Apache development team. Again, thanks a lot. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
