DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42853>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42853 Summary: mod_jk fails to pass correct path after mod_rewrite Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: Native:JK AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Software used: tomcat-connectors version 1.2.23 (self-compiled) or 1.2.18 (shipped with debian/etch), in combination with apache-2.2.3 and tomcat-5.0.28 After an upgrade of both apache and mod_jk, mod_jk no longer passes the rewritten path to tomcat, instead it sends the path as it was before mod_rewrite had its way with it. I solved the problem by downgrading to mod_jk-1.2.15, built from source. The problem was tricky to discover, as mod_jk actually logged the rewritten path when I enabled logging at loglevel debug (thus proving that mod_rewrite had already done its job). However, a tcp snooping session with wireshark revealed that it would actually send a GET request for the original, non- rewritten path. An example of the non-working situation: URL entered at the browser: http://site/snoppel mod_rewrite logs it as rewritten to: http://site/dynamic/snoppel.trp This is what shows up in mod_jk.log: [Tue Jul 10 14:45:48 2007] [15809:30912] [debug] map_uri_to_worker::jk_uri_worker_map.c (508): Attempting to map URI '/dynamic/ snoppel.trp' from 1 maps [Tue Jul 10 14:45:48 2007] [15809:30912] [debug] map_uri_to_worker::jk_uri_worker_map.c (520): Attempting to map context URI '/*' [Tue Jul 10 14:45:48 2007] [15809:30912] [debug] map_uri_to_worker::jk_uri_worker_map.c (534): Found a wildchar match mysite -> / * Which seems to indicate that it will request '/dynamic/snoppel.trp' from tomcat. But wireshark snooping the ajp13 protocol reveals a 'REQ:GET /snoppel HTTP/1.1. Which happens not to exist, and thus a HTTP 404 is returned. As mentioned, downgrading to tomcat-connectors-1.2.15 (as it was before the system upgrade) fixes this problem. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
