I was tossing this idea around as well after I couldn't get mod_webapp
to work successfully with Tomcat 4.
Tomcat might be good for HTTP but it's probably faster to employ mod_ssl
to do HTTPS.
In the proxy setup like that, what would happen to the SSL connections?
Would Tomcat have to do that kind of thing or not? And if that's done on
Apache side, what would happen to ServletRequest.isSecure() call? With
mod_jk, that's catered for...
Bojan
> "Dunlop, Aaron" wrote:
>
> Yes - it seems to work just fine with Tomcat. I've been experimenting
> with it as a possible authentication and firewall solution, and we may
> consider it as a method for load-balancing as well.
>
> We're thinking of having Apache segment our webspace by sending
> requests to different apps to different servers (e.g. a production
> server and a demonstration/sales server, both accessible from the same
> domain) Also, apache can authenticate access to certain pages using an
> LDAP database.
>
> I'm not sure this is the best solution, and Paulo's probably right
> that AJP would be more efficient, but it seems to be working so far.
>
> Just my $.02
> Aaron Dunlop
>
> -----Original Message-----
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 10, 2001 1:59 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Use of Apache proxy module to connect to Tomcat
>
> on 4/10/01 1:59 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:
>
> > Is this possible for Tomcat too? Pros and cons?
> >
> > Thanks and have fun,
> > Paulo Gaspar
>
> Of course it is.
>
> Proxy HTTP is probably not as efficient as a lightweight protocol (ie:
> AJP),
> especially if the two systems are running on the same box (ie: local
> sockets).
>
> It also doesn't solve the configuration issues.
>
> All you are doing in this case is putting another layer in front of
> the
> Tomcat HTTPd. I don't see a reason to do that when the Tomcat HTTPd
> works
> just fine. All you are gaining is the Apache module features (like
> mod_rewrite).
>
> -jon
