You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/03/28 05:43:49 UTC
DO NOT REPLY [Bug 18441] New: -
apache2/tomcat ssl non-operational
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=18441>.
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=18441
apache2/tomcat ssl non-operational
Summary: apache2/tomcat ssl non-operational
Product: Tomcat 4
Version: 4.0 Beta 1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Connector:Coyote JK 2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: dan@damon.us
Using Apache2 version 2.0.44, Tomcat 4.1.18, mod_jk 1.2.2, and openssl0.97a.
I'm fairly sure I have the configuration right, since Apache/ssl works fine
without mod_jk loaded, and Apache/Tomcat works fine when using normal http
access. However, when mod_jk is loaded, any https access results in the
following message in the apache error log, and no other action anywhere:
"Invalid method in request F"
I have used both mod_jk-2.0.43.so from the jakarta website, and also one I built
from the 1.2.2 source. Both exhibit the same problem.
The relevant portion of my Apache configuration file is:
LoadModule jk_module modules/mod_jk.so
<IfModule mod_jk.c>
Include /usr/local/tomcat/conf/auto/mod_jk.conf
JkMount /*.xml ajp13
JkExtractSSL On
JkHTTPSIndicator HTTPS
JkSESSIONIndicator SSL_SESSION_ID
JkCIPHERIndicator SSL_CIPHER
JkCERTSIndicator SSL_CLIENT_CERT
</IfModule>
Let me know if anything else is needed or I need to do an experiment.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org