It's intended to match a URL that looks like this:/johndoe/overview/p86295

The above works fine. However, if you add a period to the end of the "johndoe" part (ex: /johndoejr./overview/p86295), it causes a 404 error. If you run that string through the Helicon RegEx tester, it matches up just fine, though.

Trying the following URL, http://localhost/myserver/johndoe/overview/p86295, when I look in the rewrite log, I see that it's trying to redirect here:/myserver/johndoe/Performer.aspx?mpp_tab=overview&performerId=p86295& [INTERNAL REDIRECT]

As you can see, it's trying to pick up "johndoe" as though it's actually a real directory (which it is not).

I made a slight change to your suggested rule, placing the first slash back in it's original postion:RewriteRule ^(.*)/(.+)?/overview/(p(\+|\s|%20)*[0-9]+)(\?(.+))?$
$1/Performer.aspx?mpp_tab=overview&performerId=$3&$6 [NC,L]

This seems to work, even with a period at the end of the name. The same URL redirects to /myserver/Performer.aspx?mpp_tab=overview&performerId=p86295& as it should

I'm actually getting some inconsistent behavior that's making me think there's a bug Helicon surrounding this issue. On one of my servers, I turned logging on at the highest verbosity setting, yet when I enter a URL with a period before a slash, I get 404 error, yet absolutely NOTHING in the log (and the redirection does not work, even with the updated rewrite rule). If I enter a URL without a period before a slash, it logs it just fine.

What's even more confusing is that on my local machine, I can now get the period-before-slash URLs to work, even using my original rewrite rule.

Also note: We were previously using ISAPI REWRITE v1 last year, with the same rewrite rules, and we had no issues with these particular URLS. We didn't start seeing issues until we switched to v3.