Does Atlas updatepanel affect cookies?

I encountered a crazy and depressing problem. This is probably the case:

My website adopts form verification, so there is a login page, a page that uses Atlas updatepanel (temporarily called Atlas page), and a series of other pages. There is also a custom control myloginstatus, which is included in each page. Among them, in the Atlas page, myloginstatus is also included in the updatepanel of the Atlas page (A masterpage design error, do not want to change it, and thus found this depressing problem ).

Now I want to add the automatic logon function. Simply put, the cookie is used to remember user information. The basic process should be:
1. Create this cookie upon login
2. Check whether the cookie exists on each page that requires authentication. If so, use this cookie to create an identity ticket.
3. The cookie is deleted when you click "logout ".

Because I have made some extensions to form verification, I did not use the login series controls provided by standard 2.0. Instead, I used manual programming to call membership/formsauthentication and so on, so I had to handle them myself. It should have been a very simple problem, but the problem is: when logging out on other pages, the cookie can be cleared normally, and the page is redirected to the default page. However, after logging out from the Atlas page and redirecting to the default page, the cookie still exists, so it is logged on!

By opening the trace, we found that the cookie was cleared when the Atlas page was deregistered.CodeThe response set also contains the cookie (which is implemented by setting cookie. expires and adding it to the response set), but it does not actually work at all!

I have heard from some friends that Atlas is self-righteous and prefers to take over things that shouldn't be taken care of. Is this a great help for Atlas? This problem has not yet been clarified and is under further research.