tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GOMEZ Henri <hgo...@slib.fr>
Subject RE: Remaining Tomcat 3.3 Issues
Date Thu, 13 Sep 2001 10:12:33 GMT
>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




Mime
View raw message