Discussion:
remove the need for :8443 in URLs needing https:
Qmail List
2002-11-12 21:21:26 UTC
Permalink
Hello,

It is more difficult to re-write urls as:

https://www.domain.com:8443/index.jsp

as opposted to

https://www.domain.com/index.jsp

How can I configure Tomcat (and/or underlying Unix box) to not need the
:8443 explicit port reference in the url?

I tried changing the https /etc/services entry to port 8443 instead of 443,
but no luck.

Regards
Pae Choi
2002-11-13 00:24:50 UTC
Permalink
That is wha the connector is for.


Pae


----- Original Message -----
From: "Qmail List" <***@earthlink.net>
To: "Tomcat Users List" <tomcat-***@jakarta.apache.org>
Sent: Tuesday, November 12, 2002 1:21 PM
Post by Qmail List
Hello,
https://www.domain.com:8443/index.jsp
as opposted to
https://www.domain.com/index.jsp
How can I configure Tomcat (and/or underlying Unix box) to not need the
:8443 explicit port reference in the url?
I tried changing the https /etc/services entry to port 8443 instead of 443,
but no luck.
Regards
--
<mailto:tomcat-user-***@jakarta.apache.org>
Torsten Fohrer
2002-11-13 23:01:03 UTC
Permalink
how do you run tomcat on port 8443 or 443, with the official tomcat
distribtion you root rights for serving content on port 443 under linux.

cu Torsten Fohrer
Post by Pae Choi
That is wha the connector is for.
Pae
----- Original Message -----
Sent: Tuesday, November 12, 2002 1:21 PM
Post by Qmail List
Hello,
https://www.domain.com:8443/index.jsp
as opposted to> >
https://www.domain.com/index.jsp
How can I configure Tomcat (and/or underlying Unix box) to not need the
:8443 explicit port reference in the url?
I tried changing the https /etc/services entry to port 8443 instead of
443,
Post by Qmail List
but no luck.
Regards
--
--
Turner, John
2002-11-12 22:35:10 UTC
Permalink
This post might be inappropriate. Click to display it.
Turner, John
2002-11-14 21:51:54 UTC
Permalink
You can run Tomcat as root and have it listen on 443, as well as port 80.
This is definitely possible, though some people try to avoid running web
services as root for security reasons.

John
Post by Turner, John
-----Original Message-----
Sent: Wednesday, November 13, 2002 6:01 PM
Cc: Tomcat Users List
how do you run tomcat on port 8443 or 443, with the official tomcat
distribtion you root rights for serving content on port 443
under linux.
cu Torsten Fohrer
Post by Pae Choi
That is wha the connector is for.
Pae
----- Original Message -----
Sent: Tuesday, November 12, 2002 1:21 PM
Post by Qmail List
Hello,
https://www.domain.com:8443/index.jsp
as opposted to> >
https://www.domain.com/index.jsp
How can I configure Tomcat (and/or underlying Unix box)
to not need the
Post by Pae Choi
Post by Qmail List
:8443 explicit port reference in the url?
I tried changing the https /etc/services entry to port
8443 instead of
Post by Pae Choi
443,
Post by Qmail List
but no luck.
Regards
--
--
--
<mailto:tomcat-user-***@jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-***@jakarta.apache.org>
Torsten Fohrer
2002-11-14 23:27:20 UTC
Permalink
i run tomcat on port '80' and '443' without root rights

Torsten
Post by Turner, John
You can run Tomcat as root and have it listen on 443, as well as port 80.
This is definitely possible, though some people try to avoid running web
services as root for security reasons.
John
Post by Turner, John
-----Original Message-----
Sent: Wednesday, November 13, 2002 6:01 PM
Cc: Tomcat Users List
how do you run tomcat on port 8443 or 443, with the official tomcat
distribtion you root rights for serving content on port 443
under linux.
cu Torsten Fohrer
Post by Pae Choi
That is wha the connector is for.
Pae
----- Original Message -----
Sent: Tuesday, November 12, 2002 1:21 PM
Post by Qmail List
Hello,
https://www.domain.com:8443/index.jsp
as opposted to> >
https://www.domain.com/index.jsp
How can I configure Tomcat (and/or underlying Unix box)
to not need the
Post by Pae Choi
Post by Qmail List
:8443 explicit port reference in the url?
I tried changing the https /etc/services entry to port
8443 instead of
Post by Pae Choi
443,
Post by Qmail List
but no luck.
Regards
--
--
--
--
Brandon Cruz
2002-11-15 00:25:27 UTC
Permalink
John,

I'm using your documentation to try and connect tomcat 4.1.12 to apache
1.3.26. The page I am using is this one...
http://www.johnturner.com/howto/apache1-tomcat404-howto.html.

Anyway, I am looking at what you have for the workers.properties file and
see that you say to put a worker.ajp13.host=www.servername.com.

Does that mean we will need to create a different workers.properties file
for every virtual host, that we will need to create a separate entry for
every virtual host? My old setup just used worker.ajp13.host=localhost and
everything worked fine, but that was with tomcat 3.2.4.

Thanks for your help!

Brandon

P.S. Those documents are great, if I make any significant changes for my
configuration, I'll send them to you.
Turner, John
2002-11-15 12:59:06 UTC
Permalink
This post might be inappropriate. Click to display it.
Turner, John
2002-11-15 13:07:00 UTC
Permalink
"localhost" is fine when your Tomcat instance is on the same physical
machine as Apache.

Some folks separate the two, and others use load balancing (one Apache, many
Tomcats). With Tomcat on a separate machine from Apache, the "host"
parameter in workers.properties would be a FQDN or an IP address of the
Tomcat server.

HTH

John
Post by Turner, John
-----Original Message-----
Sent: Thursday, November 14, 2002 7:25 PM
To: Tomcat Users List
Subject: John Turner, question about your Documentation
John,
I'm using your documentation to try and connect tomcat 4.1.12
to apache
1.3.26. The page I am using is this one...
http://www.johnturner.com/howto/apache1-tomcat404-howto.html.
Anyway, I am looking at what you have for the
workers.properties file and
see that you say to put a worker.ajp13.host=www.servername.com.
Does that mean we will need to create a different
workers.properties file
for every virtual host, that we will need to create a
separate entry for
every virtual host? My old setup just used
worker.ajp13.host=localhost and
everything worked fine, but that was with tomcat 3.2.4.
Thanks for your help!
Brandon
P.S. Those documents are great, if I make any significant
changes for my
configuration, I'll send them to you.
--
Loading...