Hi all. Jumping in a bit late, but...
You have 3 options for plugging TC into Apache's URL space: 1. mod_proxy + mod_proxy_http 2. mod_proxy + mod_proxy_ajp 3. mod_jk Solution 1 is a simple proxy, works like a charm, except for one thing - it WILL NOT give you the identity of authenticated user. So, if you are using Apache for some fancy (or less fancy) authentication, TC will know nothing about it. The connection will be from Apache web server, as far as TC can say. Options 2 and 3 WILL pass the information about authenticated user (if any), so you will be able to issue "request.getRemoteUser()" and get user identifier, whatever it is. Option 2 is prefered, as of late, for it's setup simplicity, but I'm not sure where it stands in regard to balancing. mod_jk is relatively more complex to setup, but it gives a bit more control. Do you need the control is questionable. I've seen both 2 and 3 work OK. Nix. ________________________________ From: "Caldarale, Charles R" <chuck.caldar...@unisys.com> To: Tomcat Users List <users@tomcat.apache.org> Sent: Monday, February 2, 2009 10:12:57 PM Subject: RE: AJP vs HTTP connectors? > From: Gregor Schneider [mailto:rc4...@googlemail.com] > Subject: Re: AJP vs HTTP connectors? > > hm, since I'd like to avoid to browse through the whole webinar: > what are the benefits / advantages / disadvantages? I'd like to know as well, since I watched the same webinar when it was presented, and don't remember anything specific about not using AJP. (Or maybe I just tuned that part out.) - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
