Hi,

We need the default relative login.aspx?ReturnUrl=%2fdotnetnuke%2fhome.aspx

to be an absolute one: login.aspx?ReturnUrl=http%3A %2f %2fmysite.com%2mypage.html

but DNN systematically bounces back on the default, home.aspx page. Our context is http://localhost/DotNetNuke. Not sure if it would be any different in a http://dotnetnuke.mysite.com context with the portal defined as a subdomain instead of a root folder.

Help appreciated..

Yes the default provider. In the meantime we ended-up pointing ReturnUrl to a wrapper of our own, which takes care of redirecting to absolute URLs. But we'd like to stick to out-of-the-box functionality whenever possible.

It does return you to whatever page when ReturnUrl is specified the standard way as relative to the root directory of the site:

ReturnUrl=%2fdotnetnuke%2fPage3.aspx

BTW unencoded works too:

ReturnUrl=/dotnetnuke/Page3.aspx

But.. it doesn't accept ReturnUrl if specified as a complete URL with protocol and domain, which is what we need because eventually our return URL will not always be one page of the DNN site, like so:
ReturnUrl=http://otherSite.sameDomain.com/page.html

For the sake of the example, just add http://localhost like so:

ReturnUrl=http://localhost/dotnetnuke/Page3.aspx

or URL-encoded - no difference:

ReturnUrl=http%3A%2f%2flocalhost%2fdotnetnuke%2fPage3.aspx

and you'll see it'll fall back to the default to /dotnetnuke/Home.aspx, not liking the absolute ReturnUrl.