Hi,
From my experience the main difference is that AJP makes it appear as
if Apache is a listener directly attached to the Application Server,
while mod_proxy (which uses the HTTP protocol), mimics Apache as a
client. So depending on the sensitivity of your application,
that may or may not be an issue.
For instance, if your application directly relies on the servername and
port number in the request headers you would have to perform some work
arounds.
Also you cannot directly use the remodaddr value in the request as the
IP address will be that of Apache.
for remodaddr you would need to use the x-forwarded-for header value.
and for the web port you would need to configure the ajp connector with
the proxyport option.
There may be a few other things as well. I am not sure there is a
performance difference though.
glassfish_at_javadesktop.org wrote:
> Thank you.
>
> I actually managed to get something going using mod_proxy, and it seems to be working well. I found http://blogs.steeplesoft.com/virtual-hosting-using-apache-and-glassfish/ and http://www.apachetutor.org/admin/reverseproxies very helpful.
>
> Out of curiosity, is there an advantage in using mod_proxy_ajp over mod_proxy?
> [Message sent by forum member 'angusm' (angusm)]
>
> http://forums.java.net/jive/thread.jspa?messageID=287942
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
>
--
Regards
Gabe Wong
NGASI AppServer Manager
JAVA AUTOMATION and SaaS Enablement for Cloud Computing
http://www.ngasi.com
NEW! FREE Developer account for Hosted version on Amazon EC2