Dear Support,

I am having issue to login on a asp.net site hosting under the pro version. The same web page did not have any issue if I switch back to the old UltiDev Web Server. One of the sub-folders is designed as require login. So when try to access any page on this sub-folder, it is redirected to an aspx login page (as is indicated on the request URL). However, even after I enter the correct password, it won't return to the request page, nor let me view the request page by entering its URL. It is as if the state of "successful login" is not maintained. Thank you for helping.

Dear Support,

Here is what I got from the Fiddler:

POST http://localhost:2499/WWWROOT_sql2005/login.aspx?ReturnUrl=%2fWWWROOT_sql2005%2fadmin%2fadmin.aspx
302 Found to /WWWROOT_sql2005/admin/admin.aspx

GET http://localhost:2499/WWWROOT_sql2005/admin/admin.aspx
302 Found to /WWWROOT_sql2005/login.aspx?ReturnUrl=%2fWWWROOT_sql2005%2fadmin%2fadmin.aspx

GET http://localhost:2499/WWWROOT_sql2005/login.aspx?ReturnUrl=%2fWWWROOT_sql2005%2fadmin%2fadmin.aspx
200 OK (text/html)

GET http://localhost:2499/WWWROOT_sql2005/img/login.jpg
304 Not Modified (image/jpeg)

Thanks,

Wayne

Dear Support,

For some reasons Fiddler stopped tracing my application.

I believe the issue is to do with the pro version server failed to read the authentication ticket in cookies because I choose anonymous authentication.Please review the following debug process:

I did attach the process and stepped through the debugger. I find the following line in the login.aspx that does not work:

Response.Redirect(url, false); I check the url value is correct:"/wwwroot_sql2005/admin/default.aspx."

After executing the above line, it remains at Login.aspx. I speculate that the reason that it did not redirect because somehow the successful login status is not registered. The following function set the authentication ticket in cookie:

protected void SetAuthenticationTicket(string userName, string userData)
{
FormsAuthenticationTicket ticket = new FormsAuthenticationTicket(
1,
txtEmail.Text,
DateTime.Now,
DateTime.Now.AddYears(1),
chkPersistent.Checked,
userData);

string encryptedTicket = FormsAuthentication.Encrypt(ticket);
HttpCookie authenticationCookie = new HttpCookie(FormsAuthentication.FormsCookieName,encryptedTicket);
//authenticationCookie.Domain = "infomato.net";
if(chkPersistent.Checked)
authenticationCookie.Expires = ticket.Expiration;
Response.Cookies.Add(authenticationCookie);
if(Response.Cookies[authenticationCookie.Name]==null)
lblLoginMessage.Text = "Enable \'Session cookies\'";
else
lblLoginMessage.Text = "";
}

Thanks,

Wayne

Dear support,

How do I send you the fiddler file?

Thanks,

Wayne

Dear support,

Please see attached Fiddler file. The same application works on the legacy version where I can log in. In the pro version, I suspect the issue originates from either not properly write encrypted authentication cookie or not rad it back. No password was set on the attachment.

Thanks,

Wayne

Dear Support,

Yes, it does stepped into the function SetAuthenticationTicket (see attached screen shot). Please bear in mind that the exact identical code works for the legacy version.

Thank you for helping,

Wayne

Wayne,

We created a standard ASP.NET application with Forms auth and had no trouble making it work, setting auth cookies, etc.

We do not see anything wrong with your code, so we think in order for us to help you, we will need your project - or if you can create a small project for us to test that would also reproduce the problem - we will be happy to work on that and get to the bottom of the problem.

If you decide to send us your entire project, either password-protect it, or us Contact Us link first to get our email address.

Best regards,
UltiDev Team.

Sorry, we used Visual Studio 2010 - it created a project with forms auth, and we use SQL Server as membership provider, so it may not work. Could you please look up a .NET forms auth sample project on the web and see if that can be tweaked into reproducing the problem?

Best regards,
UltiDev Team.

Dear Support,

That's great! I am so glad. I am looking forward to seeing the bug fix.

Thank you so much,
Wayne

It's now official: we've got a very big bad bug that keeps only last Set-Cookie header in the response. Thank you for bringing it to our attention.

It's caused by the following bug in the .NET Framework 2.0:
http://support.microsoft.com/kb/933905

Next build will provide a fix. .NET Framework 2.0 SP1 will be required for our upcoming fix to work.

Best regards,
UltiDev Team.