Why can't we implement the 3.3 collaborative solution in 4.0 ? That would maintain compatibility.
I just hate to provide an option which could result in wrong (double escaped) behavior. At the least, it's one more variable to debug, at worst, it will generate erroneous bug reports. I'd hesitate to add it. Keith | -----Original Message----- | From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] | Sent: Monday, October 01, 2001 10:35 AM | To: [EMAIL PROTECTED] | Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI() | | | >What whould happen in 3.3 if ForwardEscapedURI was chosen? | >Wouldn't the facade escape it again? | > | | My goal in mod_jk is to keep compatibility with ALL tomcat | release, TC 3.2, 3.3 and 4.0. | | The option will let us configure it, even if by default | mod_jk found in TC 3.3 and J-T-C will use the TC 3.3 | collaborative scheme (part in Native and part in Java). | | Let's note that the JkOptions are only available in Apache | 1.3/2.0 and such flags could be needed also in IIS/NES/DOMINO |
