Failure to write cookie for IE 6?

[Guest]

Hi,

I have an Asp.Net 1.1 site which uses basic forms authentication. This
has been working fine, since way back in the 1.0 days. Twice in the last 2
months, a client has been unable to log in, once each on both her home
machine and her work machine. She gets the login screen, then gets redirected
there once again, continuously. There is no incorrect login message, and I
see a DB entry for her successful login, so I know she is using a correct
username/password. But instead of writing the cookie and moving on to the
regular admin page, she is redirected back to the login screen.

She has logged in every workday for 4 years. My code has not been changed
in the last 3 weeks.

This happens with IE 6. She has cleared her cookies, history, and temp
files, with no change. She downloads Netscape and logs in on the first try.

With IE, after clearing her cookies, she attempts a login, and is
authenticated just fine (according to the DB entry), but no cookie appears,
and back she goes to the login screen. She had a valid cookie yesterday (and
every workday for years), but if the cookie was corrupted, deleting cookies
should have fixed that, and a new one should have been written.

It's almost as if the writing of the new cookie failed on the client. Has
anyone ever heard of such a thing? Or is this absolutely something with my
(very simple) login code, even though it worked fine for years, worked 1
minute later with Netscape, and will probably work again tomorrow.

I will be updating my code over the winter to use 2.0's role-based stuff,
but I'm not sure if this will make this very intermittent problem disappear.

Thanks in advance for any help/ideas/insight.

 

[Guest]

Update: after getting home last night and looking at the code, it would
appear that it is getting all the way to the Response.Redirect line, which
sends the user to the original admin page they were aiming for (before they
were so rudely interrupted by the login page). I'm assuming that the page
that the user is being redirected to is correct, although I have now added
some debug code to verify that the next time this happens.

The only other thing I thought might be an issue is the last parameter to
Response.Redirect. In this case it is false. There is no code after this
line, so I guess this could be changed to true. But does anyone think this
could be the cause of the behavior this user is seeing? If so, any idea why
this would work fine 99% of the time, but not this time?

Once again, thanks in advance for any insight/ideas.