>Then we need to be sure to encode r->uri in the main branch
>and to change r->unparsed_uri to encode(r->uri) in the 3.2
>branch. I am swamped now and will put it on a long todo
>list.. if anyone beats me to it.....
And don't forget to port to j-t-c which is still using
for Apache 1.3/2.0 :::
/*
* The 2.2 servlet spec errata says the uri from
* HttpServletRequest.getRequestURI() should remain encoded.
* [http://java.sun.com/products/servlet/errata_042700.html]
*/
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;
}
}
What do you think about that Ryan and Frederic ?
I was planning to add JkOptions directive to mod_jk,
� la mod_ssl, may be another this could be one of the
option to tune the comportement depending people use ?
JkOptions +ForwardUnparsedURI
- 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
- Re: Remaining Tomcat 3.3 Issues Bill Barker
- 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 Ignacio J. Ortega
- RE: Remaining Tomcat 3.3 Issues Larry Isaacs
- Re: Remaining Tomcat 3.3 Issues Bill Barker
- Re: Remaining Tomcat 3.3 Issues cmanolache
- RE: Remaining Tomcat 3.3 Issues GOMEZ Henri
