tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wannamaker" <Ke...@Wannamaker.org>
Subject RE: Volunteers for: - RE: TC 3.3: getRequestURI()
Date Mon, 01 Oct 2001 13:04:38 GMT
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?

Keith


| -----Original Message-----
| From: GOMEZ Henri [mailto:hgomez@slib.fr]
| Sent: Monday, October 01, 2001 5:18 AM
| To: tomcat-dev@jakarta.apache.org
| 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 ....
|    

Mime
View raw message