Hi Chris,
That was the first thing I checked and yes, both handlers were still registered.

Hi William,

You're quite correct, the upgrade to 5.06.01 won't take care of it as it was in fact that version that I upgraded to.

The only real difference between the two handlers is that one uses a path of "*PropertyImage.jpg" and the other uses "*PropertyReport.pdf", as you can see they are both registered in the web config file with a wild card so that any paths ending with one of those two file names should be handled, however, only the .jpg handler is working, no matter what path I enter, as long as it ends with PropertyImage.jpg it is correctly handled. The pdf handler on the other hand always returns this from DNN...
Domain Name localhost/PropertyReport.pdf Does Not Exist In The Database

Regardless of where you bury it in the path...
Domain Name localhost/reports/property/PropertyReport.pdf Does Not Exist In The Database

I have come up with a workaround that seems to work but it doesn't look very good from a client perspective, I changed that file extension from pdf to axd (jpg worked too but didn't look very good requesting a jpg and getting back a pdf!) in the web config registration and obviously associated links in the module. The handler springs back into action and serves up the pdf document once more. I'd rather not have had to have done this but for now it seemed like this was the only way I could get it to work. Maybe the URLRewriteModule should check registered handlers to see if there is a handler for the requested resource prior to it applying its other rules?

Regards,
Rob

William,
I thought that would be the reason for the difference between the two, as the pdf handler would work for any image file extension.

I tried your suggestion of adding the portalid and tabid's to the query string...
http://localhost/dnn/PropertyReport.p... threw an object not set... from the URLRewriteModule.
http://localhost/dnn/PropertyReport.p... gave the domain name not in db error.
http://localhost/dnn/portalid/0/Prope... gave the domain name not in db error.
http://localhost/dnn/tabid/61/Propert...?p=3&l=en-GB loads the DNN page.

I have found that adding localhost/dnn/propertyreport.pdf as an alias for the portal brings the handler back into life but that would mean that I would need to add an alias for each of my portals aliases with propertyreport.pdf at the end of it. Now the site where this particular module is currently used only has three aliases for different domain names but if I wanted to use the above method for this handler that would increase to 6, I'm not going to go on as I'm sure you get the picture.

If the URLRewriteModule has exclusions for particular file extensions surely it could check the web.config for paths to be excluded too?