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=13820>. 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=13820 MOD_SSL Variables are inaccessable by MOD_REWRITE Summary: MOD_SSL Variables are inaccessable by MOD_REWRITE Product: Apache httpd-2.0 Version: 2.0.43 Platform: All URL: internal server (not ava OS/Version: All Status: NEW Severity: Normal Priority: Other Component: mod_ssl AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Our company tried to create an apache config that initates a redirect if the SSL_CIPHER_ALGKEYSIZE falls below 128 Bit. (We don't want to block the CIPHERS entirely). At first we tried the Syntax using Apache 1.3.27 and mod_ssl-2.8.11-1.3.27 running on Linux x86 which worked perfectly. Then we started to implement it in our 2.0.43 servers using the contributed mod_ssl running on Solaris 2.6 which did not work. Afterward we tried Apache 2.0.43 on Linux which did not work too. Finally we tried 1.3.27 Apache using mod_ssl-2.8.11-1.3.27 on Solaris 2.6 which (again) worked perfectly. We set rewrite-logging to debug mode and recognised that all the SSL_* Variables are empty but are correctly written by the ssl log using the custom log format. Afterwards we tried to run a cgi-bin script showing SSL Variables which worked again perfectly. Finally we tried to access other Environment variables using MOD_REWRITE which again worked without any problem. Question : As i heared, the mod_ssl contributed with Apache 2.0.43 is an rewriten clone of the mod_ssl module available for Apache 1.3.27. What has changed since then. Wy are the Variables inaccessable by MOD_REWRITE. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
