>Hi,
>
>If I'm not mistaken, the default for 3.3 should be JK_OPT_FWDURICOMPAT
>with re-escaping the URI for getRequestURI() being done in the facade.
>Consistent with
>this, I updated jk_isapi_plugin.c to un-escape the URI.
>
>Is this still the plan?
yes, I was wrong, but I'll keep the JkOptions
Hi,
If I'm not mistaken, the default for 3.3 should be JK_OPT_FWDURICOMPAT
with re-escaping the URI for getRequestURI() being done in the facade.
Consistent with
this, I updated jk_isapi_plugin.c to un-escape the URI.
Is this still the plan?
Larry
-Original Message-
From: [EMAIL PROTEC
>I thought what we decided to do was use
>
>s->uri = r->uri (a URI decoded already in Apache)
>
>and in the facade, re-encode it. So
>JK_OPT_FWDURICOMPAT should be the default.
Ok so there is just nothing to be done in mod_jk
isn't it just revert to old code ?
Argh, I didn't understand well wha
I thought what we decided to do was use
s->uri = r->uri (a URI decoded already in Apache)
and in the facade, re-encode it. So
JK_OPT_FWDURICOMPAT should be the default.
| -Original Message-
| + * We use JkOptions to determine which method to be used
| + *
| + * ap_
