I upgraded from an old version 4.09 to 7.3. Everything seems to be working fine except the regular expression I had setup for rewriting URLs. In 4.09 I had a rule in Friendly URL Settings (Host Settings) of the following:

MATCH: "[^?]*/Jobs/([0-9]{1,3})[a-zA-z].aspx"
REPLACE WITH: "/jobs/$1.aspx"

It works fine in 4.09 but it does not work at all in 7.3. My config is set to "advanced" for DNNFriendlyURLs config in the web.config. So, I'm wondering if these rules work when "advanced" mode is set. If so, why do you think this isn't working? If these rules no longer work in "advanced" mode, then what is my alternative to get this to work? I tried going back to "humanfriendly" and it still didn't work. 

Here's what I want to accomplish. If a URL is say "http://abcd.com/jobs/123a.aspx" then I want it to be rewritten to "http://abcd.com/jobs/123.aspx". So, the match finds 1 to 3 digits followed by a single letter and replaces it with just the numbers found and removes the letter. 123a, 123b, 123c, etc. would map to 123.

Any assistance would be greatly appreciated.

Yet another followup. I don't think the rule is even processing. I deleted the rule and find that no matter what I put after jobs other than a real page it keeps going to the jobs page with the address bar showing the intended page.

For example, if I go to /jobs/55, then it goes to 55 because I have that page and it shows what's on 55. But, if I go to /jobs/55a or /jobs/asdf or /jobs/fred or anything other than an existing page, it keeps the URL in the address bar but the page that shows is the jobs page. You would think it would go to the 404 page but it doesn't. 

Something is all messed up or I don't understand what it's doing. See screen shot below after clicking on the 59 link which should error out because 59a is not an existing page and yet it shows the jobs page with the 59a in the address bar.