HTTP and SSL Connector port problems
Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true useURIValidationHack=false Factory className= org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false protocol=TLS/ /Connector -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: HTTP and SSL Connector port problems
The reason that this is recommende is that you otherwise have to include the pot in every link. The reason why it doesn't work for you, is that ports below 1024 are restricted to users that have administrative right on the system. To use this ports you can do one of the following: - Run tomcat as administrator (If you feel comfortable with that) - Run tomcat behind IIS/Apache - Use a port mapping tool (Don't know if there is a well known for windows, I'm using mainly linux) -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 20, 2002 12:04 PM To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: HTTP and SSL Connector port problems
Sorry little typo below pot=port number -Original Message- From: Ralph Einfeldt Sent: Wednesday, November 20, 2002 12:11 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: HTTP and SSL Connector port problems The reason that this is recommende is that you otherwise have to include the pot in every link. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: HTTP and SSL Connector port problems
Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861 If you use a security-constraint confidential to force ssl you might have a problem with IE when using 8080/8443. Actually confidential should force the browser to reload a resource if you accessed it with http instead https. For Mozilla/Opera this works fine for me, with Internet Explorer the reload stalls and the browser stops loading. According to other posting you can fix it when using 80/443. I guess this is due to a url rewriting problem with IE. Maybe IE just changes the protocol from http to https instead of taking the port numbers into account aswell which can't work with non-standard ports...? The problem with IE only occurs when using non-standard ports such as 8080/8443 for http/https. If you use 80/443 you can avoid this IE bug in connection with the confidential settings. Then you don't need to hardcode absolute links. Don't know if you need that, but keep it in mind, if you use security constraints. The same problem occurs when using Apache in front of Tomcat. Tested both. IE will behave the same, so run Apache or Tomcat on 80/443 and don't forget to the the redirect ports in either the http1/1 connector and/or the Ajp-Connector. Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true useURIValidationHack=false Factory className= org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false protocol=TLS/ /Connector -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: HTTP and SSL Connector port problems
Strange! I've been testing HTTP with port 80, 8080, and even other ports for tunneling and HTTPS with port 443, 8443, and ohters for tunneling. They all work fine with IE v6.0 since TC v4.1.12 came out. Pae - Original Message - From: mech [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 3:33 AM Subject: RE: HTTP and SSL Connector port problems Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861 If you use a security-constraint confidential to force ssl you might have a problem with IE when using 8080/8443. Actually confidential should force the browser to reload a resource if you accessed it with http instead https. For Mozilla/Opera this works fine for me, with Internet Explorer the reload stalls and the browser stops loading. According to other posting you can fix it when using 80/443. I guess this is due to a url rewriting problem with IE. Maybe IE just changes the protocol from http to https instead of taking the port numbers into account aswell which can't work with non-standard ports...? The problem with IE only occurs when using non-standard ports such as 8080/8443 for http/https. If you use 80/443 you can avoid this IE bug in connection with the confidential settings. Then you don't need to hardcode absolute links. Don't know if you need that, but keep it in mind, if you use security constraints. The same problem occurs when using Apache in front of Tomcat. Tested both. IE will behave the same, so run Apache or Tomcat on 80/443 and don't forget to the the redirect ports in either the http1/1 connector and/or the Ajp-Connector. Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true useURIValidationHack=false Factory className= org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false protocol=TLS/ /Connector -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: HTTP and SSL Connector port problems
Also, everyone has different mileages. Just soemone did not able to figure out, that does not mean it's a bug. Pae Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: HTTP and SSL Connector port problems
I am already running tomcat as Administrator, but it stilll does not load. It just threw some exceptions and the window closed quickly. Did I miss something that I should I have changed in another place or file? On 20 Nov 2002 at 12:10, Ralph Einfeldt wrote: The reason that this is recommende is that you otherwise have to include the pot in every link. The reason why it doesn't work for you, is that ports below 1024 are restricted to users that have administrative right on the system. To use this ports you can do one of the following: - Run tomcat as administrator (If you feel comfortable with that) - Run tomcat behind IIS/Apache - Use a port mapping tool (Don't know if there is a well known for windows, I'm using mainly linux) -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 20, 2002 12:04 PM To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: HTTP and SSL Connector port problems
Did I miss something that I should I have changed in some other files or place? All I did was to change the ports number in server.xml On 20 Nov 2002 at 7:33, Pae Choi wrote: Strange! I've been testing HTTP with port 80, 8080, and even other ports for tunneling and HTTPS with port 443, 8443, and ohters for tunneling. They all work fine with IE v6.0 since TC v4.1.12 came out. Pae - Original Message - From: mech [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 3:33 AM Subject: RE: HTTP and SSL Connector port problems Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861 If you use a security-constraint confidential to force ssl you might have a problem with IE when using 8080/8443. Actually confidential should force the browser to reload a resource if you accessed it with http instead https. For Mozilla/Opera this works fine for me, with Internet Explorer the reload stalls and the browser stops loading. According to other posting you can fix it when using 80/443. I guess this is due to a url rewriting problem with IE. Maybe IE just changes the protocol from http to https instead of taking the port numbers into account aswell which can't work with non-standard ports...? The problem with IE only occurs when using non-standard ports such as 8080/8443 for http/https. If you use 80/443 you can avoid this IE bug in connection with the confidential settings. Then you don't need to hardcode absolute links. Don't know if you need that, but keep it in mind, if you use security constraints. The same problem occurs when using Apache in front of Tomcat. Tested both. IE will behave the same, so run Apache or Tomcat on 80/443 and don't forget to the the redirect ports in either the http1/1 connector and/or the Ajp-Connector. Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true useURIValidationHack=false Factory className= org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false protocol=TLS/ /Connector -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: HTTP and SSL Connector port problems
it may be some very simple syntax error like leaving out the / before you close the tag, it just happened to me before -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Wed 11/20/2002 2:12 PM To: Tomcat Users List Cc: Subject: Re: HTTP and SSL Connector port problems Did I miss something that I should I have changed in some other files or place? All I did was to change the ports number in server.xml On 20 Nov 2002 at 7:33, Pae Choi wrote: Strange! I've been testing HTTP with port 80, 8080, and even other ports for tunneling and HTTPS with port 443, 8443, and ohters for tunneling. They all work fine with IE v6.0 since TC v4.1.12 came out. Pae - Original Message - From: mech [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 3:33 AM Subject: RE: HTTP and SSL Connector port problems Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861 If you use a security-constraint confidential to force ssl you might have a problem with IE when using 8080/8443. Actually confidential should force the browser to reload a resource if you accessed it with http instead https. For Mozilla/Opera this works fine for me, with Internet Explorer the reload stalls and the browser stops loading. According to other posting you can fix it when using 80/443. I guess this is due to a url rewriting problem with IE. Maybe IE just changes the protocol from http to https instead of taking the port numbers into account aswell which can't work with non-standard ports...? The problem with IE only occurs when using non-standard ports such as 8080/8443 for http/https. If you use 80/443 you can avoid this IE bug in connection with the confidential settings. Then you don't need to hardcode absolute links. Don't know if you need that, but keep it in mind, if you use security constraints. The same problem occurs when using Apache in front of Tomcat. Tested both. IE will behave the same, so run Apache or Tomcat on 80/443 and don't forget to the the redirect ports in either the http1/1 connector and/or the Ajp-Connector. Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true useURIValidationHack=false Factory className= org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false protocol=TLS/ /Connector
RE: HTTP and SSL Connector port problems
I am using Windows2000 and I think it is the IIS server that is already using port 80. this prevents tomcat from using port 80. Does anyone know how to disable IIS server on Windows2000? In addition, I think some other services are using port 443 on Windows2000. Does anyone know anything about them? On 20 Nov 2002 at 14:18, brana02 wrote: it may be some very simple syntax error like leaving out the / before you close the tag, it just happened to me before -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Wed 11/20/2002 2:12 PM To: Tomcat Users List Cc: Subject: Re: HTTP and SSL Connector port problems Did I miss something that I should I have changed in some other files or place? All I did was to change the ports number in server.xml On 20 Nov 2002 at 7:33, Pae Choi wrote: Strange! I've been testing HTTP with port 80, 8080, and even other ports for tunneling and HTTPS with port 443, 8443, and ohters for tunneling. They all work fine with IE v6.0 since TC v4.1.12 came out. Pae - Original Message - From: mech [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 3:33 AM Subject: RE: HTTP and SSL Connector port problems Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861 If you use a security-constraint confidential to force ssl you might have a problem with IE when using 8080/8443. Actually confidential should force the browser to reload a resource if you accessed it with http instead https. For Mozilla/Opera this works fine for me, with Internet Explorer the reload stalls and the browser stops loading. According to other posting you can fix it when using 80/443. I guess this is due to a url rewriting problem with IE. Maybe IE just changes the protocol from http to https instead of taking the port numbers into account aswell which can't work with non-standard ports...? The problem with IE only occurs when using non-standard ports such as 8080/8443 for http/https. If you use 80/443 you can avoid this IE bug in connection with the confidential settings. Then you don't need to hardcode absolute links. Don't know if you need that, but keep it in mind, if you use security constraints. The same problem occurs when using Apache in front of Tomcat. Tested both. IE will behave the same, so run Apache or Tomcat on 80/443 and don't forget to the the redirect ports in either the http1/1 connector and/or the Ajp-Connector. Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true useURIValidationHack=false Factory className= org.apache.coyote.tomcat4
RE: HTTP and SSL Connector port problems
Disable the web server service. Would likely be called IIS Web Server or something similar. -B [EMAIL PROTECTED] 11/20/02 12:17PM I am using Windows2000 and I think it is the IIS server that is already using port 80. this prevents tomcat from using port 80. Does anyone know how to disable IIS server on Windows2000? In addition, I think some other services are using port 443 on Windows2000. Does anyone know anything about them? On 20 Nov 2002 at 14:18, brana02 wrote: it may be some very simple syntax error like leaving out the / before you close the tag, it just happened to me before -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Wed 11/20/2002 2:12 PM To: Tomcat Users List Cc: Subject: Re: HTTP and SSL Connector port problems Did I miss something that I should I have changed in some other files or place? All I did was to change the ports number in server.xml On 20 Nov 2002 at 7:33, Pae Choi wrote: Strange! I've been testing HTTP with port 80, 8080, and even other ports for tunneling and HTTPS with port 443, 8443, and ohters for tunneling. They all work fine with IE v6.0 since TC v4.1.12 came out. Pae - Original Message - From: mech [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 3:33 AM Subject: RE: HTTP and SSL Connector port problems Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861 If you use a security-constraint confidential to force ssl you might have a problem with IE when using 8080/8443. Actually confidential should force the browser to reload a resource if you accessed it with http instead https. For Mozilla/Opera this works fine for me, with Internet Explorer the reload stalls and the browser stops loading. According to other posting you can fix it when using 80/443. I guess this is due to a url rewriting problem with IE. Maybe IE just changes the protocol from http to https instead of taking the port numbers into account aswell which can't work with non-standard ports...? The problem with IE only occurs when using non-standard ports such as 8080/8443 for http/https. If you use 80/443 you can avoid this IE bug in connection with the confidential settings. Then you don't need to hardcode absolute links. Don't know if you need that, but keep it in mind, if you use security constraints. The same problem occurs when using Apache in front of Tomcat. Tested both. IE will behave the same, so run Apache or Tomcat on 80/443 and don't forget to the the redirect ports in either the http1/1 connector and/or the Ajp-Connector. Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 443 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme
