Possible Issue?

I am using IIRF v1.2.10's new -d and -f flags, and I am running into a problem. It works as expected on every 'other' request, but not on every request. What I think is happening is the -d and -f flags are keeping the values off of the last request and
checking to see if they are valid, log example below:

I've run version 1.2.11a through my system. It's running into a new problem that wasn't in the prior version. For my RegExp replacements when I want to get a capture ($1,$2,$3) I keep running into the issue where it'll capture the text I want it to, and
then it dumps it with the number behind it.

The REAL problem was with the .DEF file - it's not mentioned anywhere in the documentation as far as I can see. It took a
long time for me to find a reference to its existence online, but with that I was able to do it.

I'm going to compile the fix now - but I'll use the .10 codebase that doesn't have any of the rewrite problems with integers - going to see if it works.

It seems that the work:fail ratio is better (placebo?), but it definitely still fails to check all contents.

My version: http://neosmart.ath.cx/IsapiRewrite4.rar

Note: It has zero optimizations ATM, it's 2 am and I have to be up in 3 hours - will re-upload with optimizations tomorrow.

@Dino:
If the onurlauthcomplete and onurlmap functions aren't the problem, do you have any idea what else could be?
It's definitely a bug: keeping the F5 button pressed long enough will result in the entry being properly parsed...

Cheeso, do you have an estimate (even if it's very rough) on when IIRF v1.2.11 (or whatever the next stable version number is) will be released? Because of the issues with the -d and -f flags mentioned here, I plan to hold off on using IIRF until the next
version is released. If you aren't sure when it will come out, that's fine, but I just thought I'd check. :)