>Henri, I do not think this will be useful >or necessary with the planned changes. I'd >be -1. > >r->uri will be used, making the mod_rewrite >folks happy, and the facade will encode the >uri, which implements the spec correctly.
>Does this plan break something, the reason >you want to add an Option? The idea is to conserve compatibility with Tomcat 3.2.x and Tomcat 4.0 until they have their java side implementing the required stuff. > >Keith > > >| -----Original Message----- >| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] >| Sent: Monday, October 01, 2001 5:18 AM >| To: [EMAIL PROTECTED] >| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI() >| >| >| >| >- Revert jk/apache to use uri, remove the encode call ( >again, j-t and >| >j-t-c - one more week to do that, after that we'll be j-t-c >| >only ). Henri >| >- could you do this and the next one ? >| >| I'll reintroduce the JkOptions which will help us play with >| different encoding : >| >| ForwardStandardURI : >| >| will send just std uri >| >| s->req_uri = r->uri >| >| >| ForwardEscapedURI : >| >| will send escaped >| >| s->req_uri = ap_escape_uri(r->uri)) >| >| >| ForwardUnparsedURI : >| >| will send escaped >| >| s->req_uri = r->unparsed_uri; >| if (s->req_uri != NULL) { >| char *query_str = strchr(s->req_uri, '?'); >| if (query_str != NULL) { >| *query_str = 0; >| } >| >| We could later drop support for some options >| and make by default ForwardEscapedURI .... >| >
