no worries, mistakes happen. Thanks for the clarification on the jk exceptions. Now that you've said it it seems obvious.
I can get mod_proxy_http to work unsecurely, but once I hit the secure pages I get internal server error. Why would I not have had to do anything to enable ssl with mod_proxy_ajp? and while we're on the subject, what's the difference b/w proxyPass and ProxyPassReverse in laymens terms? thanks, c. On 3/23/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, Apologies to all. I read mod_proxy_http as mod_proxy_ajp, and made a fool of myself. Duh. - -chris Christopher Schultz wrote: > Chris, > > c. wrote: >> I'll try upping the connection timeouts, but aside from the problem >> of dropped connections what I'm really confused about is why there is >> a jk exception >> (org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)) >> when I'm using mod_proxy_ajp, NOT mod_jk. > > You aren't using mod_jk, but you are still using the JK connector (which > implements ajp13) rather than something like the HTTP connector. > > Whether you use mod_jk or mod_proxy_ajp, you are still using the Jk > connector on the Tomcat side. > > -chris > - --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGBEcU9CaO5/Lv0PARAo38AJ9fXyeZrcXzs2sBZ/j9XYOfFWd+7ACdFoeE FFTdXbES2zNsvwXw5UH0hjE= =bXy7 -----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]
