1

Closed

Broken processing in ApplyCaseConversionInPlace stomps Url Encoding opcodes

description

see http://iirf.codeplex.com/discussions/278689
 
ApplyCaseConversionInPlace stomps the trailing #E, in a #X..#E pair.
 
I don't know how this ever worked, but for sure it is not working now.
 
During processing of the replacement string, first IIRF inserts Server variables, then does case conversion, then does URL encoding. The case conversion will stomp the end-flag for url encoding, even if no case conversion is performed. The result is that no url encoding ever gets done.

file attachments

Closed Nov 11, 2011 at 11:38 AM by Cheeso
fixed in Changeset #94150 . first binary with this fix will be: v2.1.2.3

comments

Cheeso wrote Nov 2, 2011 at 6:45 PM

This is an interim build for x64 that contains a fix for this problem.

Cheeso wrote Nov 8, 2011 at 11:54 AM

Here's an interim build for x86. Please try it and tell me if it corrects the problem.

Cheeso wrote Nov 8, 2011 at 6:22 PM

Let me know if you need instructions on what to do with the zip file.

longstone2 wrote Nov 11, 2011 at 7:46 AM

Hi Chees,
sorry being late on you prompt and effective response. Had to manage deadlines :-(
Good news is it looks like we got URL-Encoding back ! (tried x86)
Server variables look OK, chars such as hyphens, apostrophes are encoded and parameter passing is ok now.
Tried also back-references and they look ok to me.
Thx! :-)

Sign in to add a comment