I had the same problem, along with several other strange bugs, using the login control.
I ended up modifying the login control. To address the issue mentioned here i changed so that the response is redirected at the end of the login button click event.
Like this:
Code:
string baseURL = getBaseURL() + "?ua=login";
Response.Redirect(baseURL, true);
and adding this function:
Code:
private static string getBaseURL()
{
string Port = library.RequestServerVariables("SERVER_PORT");
if (Port == null || Port == "80" || Port == "443")
Port = "";
else
Port = ":" + Port;
string Protocol = library.RequestServerVariables("SERVER_PORT_SECURE");
if (Protocol == null || Protocol == "0")
Protocol = "http://";
else
Protocol = "https://";
// *** Figure out the base Url which points at the application's root
return Protocol + library.RequestServerVariables("SERVER_NAME") + Port;
}
I have a feeling there should be a better way to get the "baseURL" through the umbraco api but none of the ways I tested worked well enough.
The other changes I made includes fixing the problem with the cookie expiration that always kept the user logged in for 365 days and some other problems.
I also made some major changes to the Sign Up control, the version from codeplex was hardly functional at all, the validation and other stuff being broken. I also made a way to override the default Name property of a user on sign up, as I want to be able to separate first, middle and last names.
If there is interest in these modifications I could of course post the binaries and the code somewhere... No promise however when, as my schedule is tight...
Is it me or umbraco? Umbraco Certified Professional Level 2.