One issue here:
When Apache and Tomcat are used together via AJP13:
1. The host, port, protocol, etc, are exactly that at the Apache
level, i.e. one's web app sees Apache and Tomcat as 1 entity. This is a very good thing overall compared to reverse proxying (if
that's the mod_proxy proposal).
I have no idea how to get around that ;) This seems a showstopper: the user will have to read the connector's documentation.
2. The body content, query string, etc, are reported to one's web
application precisely as sent, whereas Tomcat pre-processes them a
bit more than picky, low-level request parsing code can accept. [Yes, the "picky" code is *too* picky, but it isn't mine :-)]
I have no idea what your webapp is doing, but it's not portable. All the trasformations done respect the HTTP and servlet specifications.
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
