-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris,
c. wrote: > Filip, thanks for the info, I'll listen to anyone with good advice. So you > recommend mod_proxy_http over mod_jk? That's a good question. In two successive messages, he recommended each over the other. <shrug> > Is it the same basic setup as mod_proxy_ajp? Looking at the doc ( > http://httpd.apache.org/docs/2.0/mod/mod_proxy_http.html) it doesn't give > much info. That's because there isn't much info (at least, the last time I checked) out there. Use of mod_proxy_ajp is much simpler than mod_jk. Basically, use the same syntax for mod_proxy to proxy HTTP connections but instead you use a target URL like this: ajp://host:port/path/to/webapp While mod_proxy_ajp is easier to configure, I believe that it is severely limited by it's syntax, limiting your configuration possibilities. We can't use it because we have two workers for the same URL space, and cannot configure mod_proxy_ajp to do this. I'm not sure why Filip suggested that debugging mod_proxy_ajp would be easier than mod_jk. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGBEbJ9CaO5/Lv0PARAvETAJ4sdY+O+FPnFPH2SCtlP+tO3r/A2QCfaTbL wmRoxXK2uwhQrnYi26dK7xU= =hLqF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
