Oops, yep, that fix only went into the _32 branch. 3.3 still uses r->uri. IIRC the thread never reached a consensus, except that a proxy is free to decode and encode requests, so encode(r->uri) might be permissible, but r->unparsed_uri is the only way to preserve the encoding. Keith | -----Original Message----- | From: Larry Isaacs [mailto:[EMAIL PROTECTED]] | Sent: Wednesday, September 12, 2001 3:19 PM | To: '[EMAIL PROTECTED]' | Subject: RE: Remaining Tomcat 3.3 Issues | | | One of the main aspects of this issue is for me to | become informed as to the state of Tomcat 3.3's mod_jk | with respect to this. Tomcat 3.3's mod_jk.c has:
- RE: Remaining Tomcat 3.3 Issues Larry Isaacs
- Re: Remaining Tomcat 3.3 Issues Christopher Cain
- RE: Remaining Tomcat 3.3 Issues Larry Isaacs
- RE: Remaining Tomcat 3.3 Issues Larry Isaacs
- Re: Remaining Tomcat 3.3 Issues Bill Barker
- Re: Remaining Tomcat 3.3 Issues Bill Barker
- RE: Remaining Tomcat 3.3 Issues Keith Wannamaker
- Re: Remaining Tomcat 3.3 Issues Bill Barker
- RE: Remaining Tomcat 3.3 Issues Larry Isaacs
- Re: Remaining Tomcat 3.3 Issues David Rees
- RE: Remaining Tomcat 3.3 Issues Keith Wannamaker
- RE: Remaining Tomcat 3.3 Issues cmanolache
- RE: Remaining Tomcat 3.3 Issues Keith Wannamaker
- RE: Remaining Tomcat 3.3 Issues cmanolache
- RE: Remaining Tomcat 3.3 Issues Ignacio J. Ortega
- RE: Remaining Tomcat 3.3 Issues cmanolache
- RE: Remaining Tomcat 3.3 Issues Ignacio J. Ortega
- Re: Remaining Tomcat 3.3 Issues Bill Barker
- Re: Remaining Tomcat 3.3 Issues Craig R. McClanahan
- RE: Remaining Tomcat 3.3 Issues GOMEZ Henri
- RE: Remaining Tomcat 3.3 Issues GOMEZ Henri
