httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: 2.2.9 (Was: Re: [PROPOSAL] Time Based Releases)
Date Thu, 17 Apr 2008 12:51:33 GMT

On Apr 17, 2008, at 7:59 AM, Jess Holle wrote:
> jean-frederic clere wrote:
>>> IMHO we already forward them escaped. The problem is that things get
>>> unescaped first and for reserved characters like ';' this process
>>> cannot be reverted. So if the original URL contained an escaped ';'
>>> the forwarded one will contain a literal ';'.
>>> With mod_proxy or better ProxyPass you already can get around this
>>> by specifying the nocanon option which causes the the original
>>> URL to be forwarded (much like JkOptions +ForwardURICompatUnparsed).
>> No nocanon doesn't do that. it use url (in which the %3B is already  
>> converted in ;) instead the r->unparsed_uri.
>> And that would be JK_OPT_FWDURICOMPATUNPARSED and not  
>> ForwardURIEscaped.
>> To get ForwardURIEscaped we could call ap_escape_uri() on url.
> I can confirm that using ProxyPass and nocanon does not solve the  
> problem -- I just tested this.

Hmmm.... mod_proxy_http is aware, but methinks mod_proxy_ajp may not be
at this point :/

View raw message