"reym" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Hi there, > > Thanks for the response. I have tried that, and it works if I directly > type > in https://www.mywebsite.comin the browser (I'm using IE7). This is how my > server.xml file looks like for the non-SSL HTTP and SSL HTTP respectively: > > <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> > <Connector port="80" maxHttpHeaderSize="8192" > maxThreads="150" minSpareThreads="25" maxSpareThreads="75" > enableLookups="false" redirectPort="8443" acceptCount="100" > connectionTimeout="20000" disableUploadTimeout="true" > /> > > <!-- Define a SSL HTTP/1.1 Connector on port 8443 --> > <Connector port="443" maxHttpHeaderSize="8192" > > className="org.apache.catalina.connector.http.HttpConnector"
This is sooooooo deprecated and buggy. You should use the default Coyote Connector instead. > maxThreads="150" > minSpareThreads="25" > maxSpareThreads="75" > enableLookups="false" > disableUploadTimeout="true" > acceptCount="100" > scheme="https" > secure="true" > clientAuth="false" > sslProtocol="TLS" > keystoreFile="/root/.keystore" > keystoreType="JKS" > keystorePass="b0nus2ooo??" > > > <Factory className="org.apache.catalina.net.SSLServerSocketFactory" > clientAuth="false" protocol="TLS"/> > </Connector> > > > I'm not using a .htaccess file. What am i missing? I read something about > a > redirectPort attribute, am i suppose to be using that? Please advise. > Yes, the redirectPort attribute needs to match the port for the SSL Connector (in your case, 443). And it's a good thing, since IE has issues on 4.1.x when you try and use a non-default port for the SSL Connector. > Thank you for your time, and thanks in advance. I look forward to hearing > from you. > > > Kind regards, > Rey Malahay > > > > Caldarale, Charles R wrote: >> >>> From: reym [mailto:[EMAIL PROTECTED] >>> Subject: .htaccess + Tomcat >>> >>> I have installed SSL on the server, and would like >>> to use a .htaccess file so that when a user types in >>> http://www.mywebsite.com he/ she will be redirected >>> to https://www.mywebsite.com automatically. >> >> You need to become familiar with the servlet spec: >> http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index.html >> >> In particular, look at section 12.7 for a <transport-guarantee> of >> CONFIDENTIAL. >> >> If you want all of your webapps to use HTTPS, you can put the >> <transport-guarantee> in conf/web.xml rather than in the WEB-INF/web.xml >> of each of the individual webapps. >> >> - Chuck >> >> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >> MATERIAL and is thus for use only by the intended recipient. If you >> received this in error, please contact the sender and delete the e-mail >> and its attachments from all computers. >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/.htaccess-%2B-Tomcat-tf3899482.html#a11072000 > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
