It should be listening on the primary interface by default. So if
you are running Geronimo on the server hosted by your ISP, and the
ISP allows traffic to port 8080, then you can simply point your we-
browser at http://<your_ip>:8080
--jason
On Dec 19, 2006, at 6:02 PM, Ray Hurst wrote:
So it can be used in standalone mode...great. I have been using it
as a localhost for a couple of days now.
How do I get it to respond to the outside world?
In other words, I want to be able to type in the IP address given
to me by my ISP and have Geronimo respond.
--ray
Jason Dillon wrote:
No, you do not need Apache HTTPD, you can use the webcontainer
that comes in Geronimo (either Tomcat or Jetty depending on which
distribution you pick). If you want you can setup an AJP
connector from the webcontainer in Geronimo to allow an Apache
HTTPD to integration with Geronimo seamlessly. This is handy if
you have other apps that you need to run that are in PHP (or
something) and want to present your users with a single URL to
access both (otherwise you'd need 2 urls, one for HTTPD and one
for Geronimo).
HTTPD also makes a nice SSL accelerator for use with Geronimo
applications, so you can configure HTTPD to use SSL, setup AJP to
connect up Geronimo, and then block off all other ports to
Geronimo so that the site is more secure.
--jason
On Dec 19, 2006, at 5:03 PM, Ray Hurst wrote:
Can Geronimo be the web server or does it need be a back end to
Apache?
Are there docs that explain the advantages and disadvantages?
I am an extreme newbie?
Ray
