I am having a weird issue that I am not sure how to fix.  Maybe there is a setting somewhere in DNN I don't know about?

The problem:  If you login to a portal, then let it sit until your login expires, once you click to go to another page (a page that at least is locked down to registered users) you get redirected to the login page.  In the url of the login page I see something like this: https://www.hostname.com/login?returnurl=/mid/1350?portalid=2.  This is okay UNLESS the link you are clicking on includes some query string parameters.  For instance, lets say I have a list of people that will link to a detailed page when you click on a person.  If I click on the link after expiration, the URL on the login page would look like this: /People/PersonDetail/mid/1294?ID=123456.  Take the same list show idle long enough for your login to expire.  When you click on a person you will be redirected to the login page.  The url now looks like this:  https://www.hostname.com/login?returnurl=/People/PersonDetail/mid/1294?ID=123456?portalid=2.  It appears that the system just tacks on ?portalid=2 to the end of whatever url I clicked on.  Of course after logon, the system redirects me to the /People/PersonDetail/mid/1294 page and I get an error because ID 123456?portalid=2 does not exist.....

How can I keep the system from tacking that on at the end?  Or is this a bug I should file?  Or can I configure something that makes this work?  Or am I using query strings incorrectly with DNN?

Thanks!