The one really compelling /usability /bit about AJP proxying is that
requests look like you're in/at the web server in question and receiving
requests directly from the client of the web server.
The fact that you are not is completely and utterly transparent to your
web application code.
The same cannot be said for HTTP proxying, which throws the proxying
details in your face and leaves you scrambling with various valves, etc,
to hide these details from web applications that care about the logical,
not physical, truth of the situation.
--
Jess Holle
