shawnwhite
New Member
Hi, I'm using Forms Authentication (with a cookieless session) to manage the security of my site and I'm having some trouble with certain machines gaining access. On most machines in my office I can attempt to open default.aspx and I'm redirected to login.aspx. After logging in I am redirected to default.aspx and everything works fine. However, on the odd machine (using IE 5.5) I am sent to the login page from default.aspx, but upon logging in, the login page just refreshes and I'm not forwarded to default.aspx.<BR><BR>I've been through article after article about Forms Authentication and I can't seem to find anything that addresses this. Any ideas?This is a quote from a 4guysfromrolla.com article:<BR><BR>"ASP.NET uses url 'munging' (rewriting), to allow session state to be maintained without the use of cookies but it does not provide support for cookieless FormsAuthentication. The developer of the Web application has to write code to do it."<BR><BR>http://www.4guysfromrolla.com/webtech/110701-1.2.shtml<BR><BR>Obviously this does not help you, but from the reading I've done, FormsAuthentication relies on cookies heavily. The two will not be mutually exclusive until you roll your own code to take care of the redirection.<BR><BR>Since I've searched a massive amount of forums and sites on this very issue in the last 2 days and you posted your question in May, did you ever find an answer to this problem?For any that may read this in utter frustration looking for a solution, here is the solution:<BR><BR>http://support.microsoft.com/default.aspx?scid=kb;EN-US;q316112 <BR><BR>We discovered that issues with session variables not working are related to forms authentication not working. The problem is machines with an underscore in their name. To solve, we set the default page in the application directory to an asp page with one line of code:<BR><BR><%<BR>Response.Redirect("http://" & Request.ServerVariables("LOCAL_ADDR") & "/default.aspx")<BR>%><BR><BR>This redirects to the IP address and solves all the freakin' problems. Of course, in the tradition of all impossible microsoft problems, this behaviour is by design.<BR><BR>