I would seldom dare to differ with Mark with regards to Tomcat issues
but in this case, I prefer mod_AJP for its more
predictive behavior compared to mod_HTTP. Tomcat AJP's connector
simulates almost the same behavior as Tomcat's HTTP connector.
So the all important request headers will look the
Mark Thomas:
Generally, and YMMV, mod_proxy_http is more stable. This is only a
generalisation though. I have used mod_proxy_ajp in the past without any
problems.
Ah, OK.
Since the mod_proxy_ajp setup I use is extremely simple and for a
low-volume site, I don't expect any problems.
Other r
Markus Schönhaber wrote:
> Mark Thomas:
>
>> Actually, mod_proxy_http is usually a better choice than mod_proxy_ajp
>
> Could you please explain a little further?
> Since at one site I'm using mod_proxy_ajp I'm interested in what the
> advantage of switching to mod_proxy_http might be.
Generally
Mark Thomas:
Actually, mod_proxy_http is usually a better choice than mod_proxy_ajp
Could you please explain a little further?
Since at one site I'm using mod_proxy_ajp I'm interested in what the
advantage of switching to mod_proxy_http might be.
Regards
mks
-
Gabe Wong wrote:
> Jeff try:
>
> ProxyPass /app1
> http://localhost:8080/app1
> ProxyPassReverse /app1 http://localhost:8080/app1
>
> and better yet if your have mod_proxy_ajp:
> ProxyPass /app1 ajp://localhost:8009/app1
> ProxyPassRev
Jeff try:
ProxyPass /app1 http://localhost:8080/app1
ProxyPassReverse /app1 http://localhost:8080/app1
and better yet if your have mod_proxy_ajp:
ProxyPass /app1 ajp://localhost:8009/app1
ProxyPassReverse /app1 ajp://localhost:8009
Hi All,
I'm having some issues with some apps I am running on my server. I'm
running multiple apps in tomcat and serving up each of them through
apache with mod_proxy. Most of these are working great, but there are a
few that don't seem to want to co-operate. I currently have my proxies set
up i
