I've got a fairly simple forms authentication project (a login page and a
single secure page), but a number of users (~25%) can't seem to get past the
login.aspx step. I theorized that this might have to do with their
browser's cookie setting.
I had been using cookies to store session state and logon parameters (user
option), but I completely eliminated them using the SQLServer session
management approach. But now, with my test browser set on "prompt" for
cookies, I still get a message that my login page is trying to set a cookie.
I gather it's from this statement: