Hi Dave, I had precisely the same problem. It is an issue with the layout of the httpd.conf.
Here is the solution: 1. Place the LoadModule and the WebAppConnection directives before the 'Port 80' directive for the Main Server Configuration. 2. Place the WebAppDeploy directive immediately after the ServerName directive. I used the above procedure to fix the problem. I think the general issue here is that: typically, we place the WebAppDeploy directive at the end of the .conf file. That leaves the VirtualHost listening on 443 without the benefit of the deployment. By placing the directive with the Main Server config, we allow all VirtualHosts (including the one on 443) to inherit it. - Yesho. -----Original Message----- From: Dave North [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 22, 2002 8:10 AM To: Tomcat Users List Subject: RE: wacky HTTPS->HTTP re-direct problem w/apache and tomcat 4 I'm beginning to think it is in the server.xml. here ya go. I don't think I've made any changes here but..... The relevant stuff is at the end I guess (the warp connector) <!-- Example Server Configuration File --> <!-- Note that component elements are nested corresponding to their parent-child relationships with each other --> <!-- A "Server" is a singleton element that represents the entire JVM, which may contain one or more "Service" instances. The Server listens for a shutdown command on the indicated port. Note: A "Server" is not itself a "Container", so you may not define subcomponents such as "Valves" or "Loggers" at this level. --> <Server port="8005" shutdown="SHUTDOWN" debug="0"> <!-- A "Service" is a collection of one or more "Connectors" that share a single "Container" (and therefore the web applications visible within that Container). Normally, that Container is an "Engine", but this is not required. Note: A "Service" is not itself a "Container", so you may not define subcomponents such as "Valves" or "Loggers" at this level. --> <!-- Define the Tomcat Stand-Alone Service --> <Service name="Tomcat-Standalone"> <!-- A "Connector" represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated "Container" (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 4.0 documentation bundle for more detailed instructions): * Download and install JSSE 1.0.2 or later, and put the JAR files into "$JAVA_HOME/jre/lib/ext". * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of "changeit" for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the "enableLookups" attribute to "false". When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. --> <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8080" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="60000"/> <!-- Note : To disable connection timeouts, set connectionTimeout value to -1 --> <!-- Define an SSL HTTP/1.1 Connector on port 8443 --> <!-- <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" scheme="https" secure="true"> <Factory className="org.apache.catalina.net.SSLServerSocketFactory" clientAuth="false" protocol="TLS"/> </Connector> --> <!-- Define an AJP 1.3 Connector on port 8009 --> <!-- <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" port="8009" minProcessors="5" maxProcessors="75" acceptCount="10" debug="0"/> --> <!-- Define a Proxied HTTP/1.1 Connector on port 8081 --> <!-- See proxy documentation for more information about using this. --> <!-- <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8081" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" connectionTimeout="60000" proxyPort="80"/> --> <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 --> <!-- <Connector className="org.apache.catalina.connector.http10.HttpConnector" port="8082" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0"/> --> <!-- An Engine represents the entry point (within Catalina) that processes every request. The Engine implementation for Tomcat stand alone analyzes the HTTP headers included with the request, and passes them on to the appropriate Host (virtual host). --> <!-- Define the top level container in our container hierarchy --> <Engine name="Standalone" defaultHost="localhost" debug="0"> <!-- The request dumper valve dumps useful debugging information about the request headers and cookies that were received, and the response headers and cookies that were sent, for all requests received by this instance of Tomcat. If you care only about requests to a particular virtual host, or a particular application, nest this element inside the corresponding <Host> or <Context> entry instead. For a similar mechanism that is portable to all Servlet 2.3 containers, check out the "RequestDumperFilter" Filter in the example application (the source for this filter may be found in "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters"). Request dumping is disabled by default. Uncomment the following element to enable it. --> <!-- <Valve className="org.apache.catalina.valves.RequestDumperValve"/> --> <!-- Global logger unless overridden at lower levels --> <Logger className="org.apache.catalina.logger.FileLogger" prefix="catalina_log." suffix=".txt" timestamp="true"/> <!-- Because this Realm is here, an instance will be shared globally --> <Realm className="org.apache.catalina.realm.MemoryRealm" /> <!-- Replace the above Realm with one of the following to get a Realm stored in a database and accessed via JDBC --> <!-- <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" driverName="org.gjt.mm.mysql.Driver" connectionURL="jdbc:mysql://localhost/authority?user=test;password=tes t" userTable="users" userNameCol="user_name" userCredCol="user_pass" userRoleTable="user_roles" roleNameCol="role_name" /> --> <!-- <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" driverName="oracle.jdbc.driver.OracleDriver" connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL?user=scott;passwor d=tiger" userTable="users" userNameCol="user_name" userCredCol="user_pass" userRoleTable="user_roles" roleNameCol="role_name" /> --> <!-- <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99" driverName="sun.jdbc.odbc.JdbcOdbcDriver" connectionURL="jdbc:odbc:CATALINA" userTable="users" userNameCol="user_name" userCredCol="user_pass" userRoleTable="user_roles" roleNameCol="role_name" /> --> <!-- Define the default virtual host --> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true"> <!-- Normally, users must authenticate themselves to each web app individually. Uncomment the following entry if you would like a user to be authenticated the first time they encounter a resource protected by a security constraint, and then have that user identity maintained across *all* web applications contained in this virtual host. --> <!-- <Valve className="org.apache.catalina.authenticator.SingleSignOn" debug="0"/> --> <!-- Access log processes all requests for this virtual host. By default, log files are created in the "logs" directory relative to $CATALINA_HOME. If you wish, you can specify a different directory with the "directory" attribute. Specify either a relativ e (to $CATALINA_HOME) or absolute path to the desired directory. --> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="common"/> <!-- Logger shared by all Contexts related to this virtual host. By default (when using FileLogger), log files are created in the "logs " directory relative to $CATALINA_HOME. If you wish, you can specify a different directory with the "directory" attribute. Specify eith er a relative (to $CATALINA_HOME) or absolute path to the desired directory.--> <Logger className="org.apache.catalina.logger.FileLogger" directory="logs" prefix="localhost_log." suffix=".txt" timestamp="true"/> <!-- Define properties for each web application. This is only needed if you want to set non-default properties, or have web application document roots in places other than the virtual host's appBase directory. --> <!-- Tomcat Root Context --> <!-- <Context path="" docBase="ROOT" debug="0"/> --> <!-- Tomcat Manager Context --> <Context path="/manager" docBase="manager" debug="0" privileged="true"/> <!-- Tomcat Examples Context --> <Context path="/examples" docBase="examples" debug="0" reloadable="true"> <Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_examples_log." suffix=".txt" timestamp="true"/> <Ejb name="ejb/EmplRecord" type="Entity" home="com.wombat.empl.EmployeeRecordHome" remote="com.wombat.empl.EmployeeRecord"/> <!-- PersistentManager: Uncomment the section below to test Persistent Sessions. saveOnRestart: If true, all active sessions will be saved to the Store when Catalina is shutdown, regardless of other settings. All Sessions found in the Store will be loaded on startup. Sessions past their expiration are ignored in both cases. maxActiveSessions: If 0 or greater, having too many active sessions will result in some being swapped out. minIdleSwap limits this. -1 means unlimited sessions are allowed. 0 means sessions will almost always be swapped out after use - this will be noticeably slow for your users. minIdleSwap: Sessions must be idle for at least this long (in seconds) before they will be swapped out due to maxActiveSessions. This avoids thrashing when the site is highly active. -1 or 0 means there is no minimum - sessions can be swapped out at any time. maxIdleSwap: Sessions will be swapped out if idle for this long (in seconds). If minIdleSwap is higher, then it will override this. This isn't exact: it is checked periodically. -1 means sessions won't be swapped out for this reason, although they may be swapped out for maxActiveSessions. If set to >= 0, guarantees that all sessions found in the Store will be loaded on startup. maxIdleBackup: Sessions will be backed up (saved to the Store, but left in active memory) if idle for this long (in seconds), and all sessions found in the Store will be loaded on startup. If set to -1 sessions will not be backed up, 0 means they should be backed up shortly after being used. To clear sessions from the Store, set maxActiveSessions, maxIdleS wap, and minIdleBackup all to -1, saveOnRestart to false, then restart Catalina. --> <!-- <Manager className="org.apache.catalina.session.PersistentManager" debug="0" saveOnRestart="true" maxActiveSessions="-1" minIdleSwap="-1" maxIdleSwap="-1" maxIdleBackup="-1"> <Store className="org.apache.catalina.session.FileStore"/> </Manager> --> <Environment name="maxExemptions" type="java.lang.Integer" value="15"/> <Parameter name="context.param.name" value="context.param.value" override="false"/> <Resource name="jdbc/EmployeeAppDb" auth="SERVLET" type="javax.sql.DataSource"/> <ResourceParams name="jdbc/EmployeeAppDb"> <parameter><name>user</name><value>sa</value></parameter> <parameter><name>password</name><value></value></parameter> <parameter><name>driverClassName</name> <value>org.hsql.jdbcDriver</value></parameter> <parameter><name>driverName</name> <value>jdbc:HypersonicSQL:database</value></parameter> </ResourceParams> <Resource name="mail/Session" auth="Container" type="javax.mail.Session"/> <ResourceParams name="mail/Session"> <parameter> <name>mail.smtp.host</name> <value>localhost</value> </parameter> </ResourceParams> </Context> </Host> </Engine> </Service> <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0 as its servlet container. Please read the README.txt file coming with the WebApp Module distribution on how to build it. (Or check out the "jakarta-tomcat-connectors/webapp" CVS repository) To configure the Apache side, you must ensure that you have the "ServerName" and "Port" directives defined in "httpd.conf". Then, lines like these to the bottom of your "httpd.conf" file: LoadModule webapp_module libexec/mod_webapp.so WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples warpConnection /examples/ The next time you restart Apache (after restarting Tomcat, if needed) the connection will be established, and all applications you make visible via "WebAppDeploy" directives can be accessed through Apache. --> <!-- Define an Apache-Connector Service --> <Service name="Tomcat-Apache"> <Connector className="org.apache.catalina.connector.warp.WarpConnector" port="8008" minProcessors="5" maxProcessors="75" enableLookups="true" scheme="https" secure="true" acceptCount="10" debug="0"/> <!-- Replace "localhost" with what your Apache "ServerName" is set to --> <Engine className="org.apache.catalina.connector.warp.WarpEngine" name="Apache" debug="0" appBase="webapps"> <!-- Global logger unless overridden at lower levels --> <Logger className="org.apache.catalina.logger.FileLogger" prefix="apache_log." suffix=".txt" timestamp="true"/> <!-- Because this Realm is here, an instance will be shared globally --> <Realm className="org.apache.catalina.realm.MemoryRealm" /> </Engine> </Service> </Server> -----Original Message----- From: Denny Chambers [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 22, 2002 10:11 AM To: Tomcat Users List Subject: Re: wacky HTTPS->HTTP re-direct problem w/apache and tomcat 4 This is really strange. I have the same setup. I set the Server Name directive once in the main portion of the httpd.conf. My <VirtualHost _default_:443> context is very similar to yours, except I don't have the Server Name defined with in it. My WebAppConnection and WebAppDeploy line are similar as well, I use localhost as my server name in the WebAppConnection directive. What about your server.xml, let's see what that looks like. I kind of running out of suggestions. sorry! Dave North wrote: > > Hi Denny, > Just tried that - no joy. It then complains about the > webAppDeploy lines being an invalid serverName. > > Cheers > > Dave > > -----Original Message----- > From: Denny Chambers [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 4:52 PM > To: Tomcat Users List > Subject: Re: wacky HTTPS->HTTP re-direct problem w/apache and tomcat 4 > > Have you tried it with out the ServerName directive set in the > <VirtualHost _default_:443> directive? > > "Chambers, Norman (Denny)" wrote: > > > > If tomcat and apache are running on the try using localhost:8080 here: > > > > WebAppConnection myconn warp ottas13a.ott.signiant.com:8008 > > > > Also do you have the ServerName and Port directive set in the > > httpd.conf? The directives are required by SSL. > > > > Dave North wrote: > > > > > > sure. Actually, back in the mailing list archive I just found > someone > > > who had the exact same problem...no solution alas. > > > > > > The server.xml file is the bog standard one with no changes from a > > > tomcat install. > > > > > > My httpd.conf info (basically the standard mod_ssl config with the > > > webAppDeploy stuff bolted in): > > > > > > ## > > > ## SSL Virtual Host Context > > > ## > > > > > > <VirtualHost _default_:443> > > > > > > # General setup for the virtual host > > > DocumentRoot "/usr/local/apache/htdocs" > > > ServerName ottas13a.ott.signiant.com > > > ServerAdmin [EMAIL PROTECTED] > > > ErrorLog /usr/local/apache/logs/error_log > > > TransferLog /usr/local/apache/logs/access_log > > > > > > # SSL Engine Switch: > > > # Enable/Disable SSL for this virtual host. > > > SSLEngine on > > > > > > # SSL Cipher Suite: > > > # List the ciphers that the client is permitted to negotiate. > > > # See the mod_ssl documentation for a complete list. > > > SSLCipherSuite > > > ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL > > > > > > # Server Certificate: > > > # Point SSLCertificateFile at a PEM encoded certificate. If > > > # the certificate is encrypted, then you will be prompted for a > > > # pass phrase. Note that a kill -HUP will prompt again. A test > > > # certificate can be generated with `make certificate' under > > > # built time. Keep in mind that if you've both a RSA and a DSA > > > # certificate you can configure both in parallel (to also allow > > > # the use of DSA ciphers, etc.) > > > SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt > > > #SSLCertificateFile /usr/local/apache/conf/ssl.crt/server-dsa.crt > > > > > > # Server Private Key: > > > # If the key is not combined with the certificate, use this > > > # directive to point at the key file. Keep in mind that if > > > # you've both a RSA and a DSA private key you can configure > > > # both in parallel (to also allow the use of DSA ciphers, etc.) > > > SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key > > > #SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server-dsa.key > > > > > > # Server Certificate Chain: > > > # Point SSLCertificateChainFile at a file containing the > > > # concatenation of PEM encoded CA certificates which form the > > > # certificate chain for the server certificate. Alternatively > > > # the referenced file can be the same as SSLCertificateFile > > > # when the CA certificates are directly appended to the server > > > # certificate for convinience. > > > #SSLCertificateChainFile /usr/local/apache/conf/ssl.crt/ca.crt > > > > > > # Certificate Authority (CA): > > > # Set the CA certificate verification path where to find CA > > > # certificates for client authentication or alternatively one > > > # huge file containing all of them (file must be PEM encoded) > > > # Note: Inside SSLCACertificatePath you need hash symlinks > > > # to point to the certificate files. Use the provided > > > # Makefile to update the hash symlinks after changes. > > > #SSLCACertificatePath /usr/local/apache/conf/ssl.crt > > > #SSLCACertificateFile /usr/local/apache/conf/ssl.crt/ca-bundle.crt > > > > > > # Certificate Revocation Lists (CRL): > > > # Set the CA revocation path where to find CA CRLs for client > > > # authentication or alternatively one huge file containing all > > > # of them (file must be PEM encoded) > > > # Note: Inside SSLCARevocationPath you need hash symlinks > > > # to point to the certificate files. Use the provided > > > # Makefile to update the hash symlinks after changes. > > > #SSLCARevocationPath /usr/local/apache/conf/ssl.crl > > > #SSLCARevocationFile /usr/local/apache/conf/ssl.crl/ca-bundle.crl > > > > > > # Client Authentication (Type): > > > # Client certificate verification type and depth. Types are > > > # none, optional, require and optional_no_ca. Depth is a > > > # number which specifies how deeply to verify the certificate > > > # issuer chain before deciding the certificate is not valid. > > > #SSLVerifyClient require > > > #SSLVerifyDepth 10 > > > > > > # Access Control: > > > # With SSLRequire you can do per-directory access control based > > > # on arbitrary complex boolean expressions containing server > > > # variable checks and other lookup directives. The syntax is a > > > # mixture between C and Perl. See the mod_ssl documentation > > > # for more details. > > > #<Location /> > > > #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ > > > # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \ > > > # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \ > > > # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ > > > # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ > > > # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ > > > #</Location> > > > > > > # SSL Engine Options: > > > # Set various options for the SSL engine. > > > # o FakeBasicAuth: > > > # Translate the client X.509 into a Basic Authorisation. This > means > > > that > > > # the standard Auth/DBMAuth methods can be used for access > control. > > > The > > > # user name is the `one line' version of the client's X.509 > > > certificate. > > > # Note that no password is obtained from the user. Every entry > in > > > the user > > > # file needs this password: `xxj31ZMTZzkVA'. > > > # o ExportCertData: > > > # This exports two additional environment variables: > SSL_CLIENT_CERT > > > and > > > # SSL_SERVER_CERT. These contain the PEM-encoded certificates of > the > > > # server (always existing) and the client (only existing when > client > > > # authentication is used). This can be used to import the > > > certificates > > > # into CGI scripts. > > > # o StdEnvVars: > > > # This exports the standard SSL/TLS related `SSL_*' environment > > > variables. > > > # Per default this exportation is switched off for performance > > > reasons, > > > # because the extraction step is an expensive operation and is > > > usually > > > # useless for serving static content. So one usually enables the > > > # exportation for CGI and SSI requests only. > > > # o CompatEnvVars: > > > # This exports obsolete environment variables for backward > > > compatibility > > > # to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold > 2.x. > > > Use this > > > # to provide compatibility to existing CGI scripts. > > > # o StrictRequire: > > > # This denies access when "SSLRequireSSL" or "SSLRequire" > applied > > > even > > > # under a "Satisfy any" situation, i.e. when it applies access > is > > > denied > > > # and no other module can change it. > > > # o OptRenegotiate: > > > # This enables optimized SSL connection renegotiation handling > when > > > SSL > > > # directives are used in per-directory context. > > > #SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars > +StrictRequire > > > <Files ~ "\.(cgi|shtml|phtml|php3?)$"> > > > SSLOptions +StdEnvVars > > > </Files> > > > <Directory "/usr/local/apache/cgi-bin"> > > > SSLOptions +StdEnvVars > > > </Directory> > > > > > > # SSL Protocol Adjustments: > > > # The safe and default but still SSL/TLS standard compliant > shutdown > > > # approach is that mod_ssl sends the close notify alert but > doesn't > > > wait for > > > # the close notify alert from client. When you need a different > > > shutdown > > > # approach you can use one of the following variables: > > > # o ssl-unclean-shutdown: > > > # This forces an unclean shutdown when the connection is closed, > > > i.e. no > > > # SSL close notify alert is send or allowed to received. This > > > violates > > > # the SSL/TLS standard but is needed for some brain-dead > browsers. > > > Use > > > # this when you receive I/O errors because of the standard > approach > > > where > > > # mod_ssl sends the close notify alert. > > > # o ssl-accurate-shutdown: > > > # This forces an accurate shutdown when the connection is > closed, > > > i.e. a > > > # SSL close notify alert is send and mod_ssl waits for the close > > > notify > > > # alert of the client. This is 100% SSL/TLS standard compliant, > but > > > in > > > # practice often causes hanging connections with brain-dead > > > browsers. Use > > > # this only for browsers where you know that their SSL > > > implementation > > > # works correctly. > > > # Notice: Most problems of broken clients are also related to the > HTTP > > > # keep-alive facility, so you usually additionally want to disable > > > # keep-alive for those clients, too. Use variable "nokeepalive" > for > > > this. > > > # Similarly, one has to force some clients to use HTTP/1.0 to > > > workaround > > > # their broken HTTP/1.1 implementation. Use variables > "downgrade-1.0" > > > and > > > # "force-response-1.0" for this. > > > SetEnvIf User-Agent ".*MSIE.*" \ > > > nokeepalive ssl-unclean-shutdown \ > > > downgrade-1.0 force-response-1.0 > > > > > > # Per-Server Logging: > > > # The home of a custom SSL log file. Use this when you want a > > > # compact non-error SSL logfile on a virtual host basis. > > > CustomLog /usr/local/apache/logs/ssl_request_log \ > > > "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" > > > > > > # DN for tomcat > > > WebAppConnection myconn warp ottas13a.ott.signiant.com:8008 > > > WebAppDeploy examples myconn /examples/ > > > WebAppDeploy signiant myconn /signiant/ > > > WebAppInfo /webapp-info > > > > > > </VirtualHost> > > > > > > -----Original Message----- > > > From: Denny Chambers [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, January 21, 2002 4:10 PM > > > To: Tomcat Users List > > > Subject: Re: wacky HTTPS->HTTP re-direct problem w/apache and tomcat > 4 > > > > > > I have this same setup working with out any problems. Can you send > the > > > section of the httpd.conf where you setup the https server. In > tomcat > > > are you using both the http connector and the warp connector? Not > sure > > > if this would cause a problem or not, I am only using the warp > connector > > > by itself. > > > > > > Dave North wrote: > > > > > > > > Hello all, > > > > I have the following config: > > > > > > > > apache 1.3.2.2 using mod_ssl and mod_webapp > > > > tomcat 4.0.1 > > > > RH Linux 7.1 > > > > > > > > I had successfully configured apache to talk via the warp > connector to > > > > tomcat for our JSP application. Now I wanted to add SSL support > so I > > > > downloaded and installed mod_ssl. No problems so far. However, > when > > > I > > > > go to https://myhost/myapp/ it fails because it's re-directed me > to > > > > http://myhost:443/myapp/index.jsp. I have the same problem with > the > > > > examples. When served from tomcat directly (in http, no problems. > > > > > > > > I can't seem to find anything on this problem and it's driving me > > > crazy! > > > > :) > > > > > > > > Snippet from my httpd.conf: > > > > > > > > # DN for tomcat > > > > WebAppConnection myconn warp localhost:8008 > > > > WebAppDeploy examples myconn /examples/ > > > > WebAppDeploy myapp myconn /myapp/ > > > > WebAppInfo /webapp-info > > > > > > > > I'm just using the standard server.xml for tomcat. > > > > > > > > Any help is MUCH appreciated. > > > > > > > > Cheers > > > > > > > > Dave > > > > > > > > Dave North > > > > SIGNIANT Inc. > > > > Trusted Data Transfer Services > > > > www.signiant.com > > > > Phone: 613-761-3623 > > > > Fax: 613-761-3629 > > > > EMail: [EMAIL PROTECTED] > > > > > > > > -- > > > > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > > > > For additional commands: > <mailto:[EMAIL PROTECTED]> > > > > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > > > For additional commands: > <mailto:[EMAIL PROTECTED]> > > > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > > > For additional commands: > <mailto:[EMAIL PROTECTED]> > > > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > > > > -- > > > > > -- > > To unsubscribe: <mailto:[EMAIL PROTECTED]> > > For additional commands: <mailto:[EMAIL PROTECTED]> > > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
