How to solve the problem of cookie value loss and garbled code when the cookie value in Asp.net 2.0 is medium

When the total number of stored values in cookies is lost today, is there a limit on the number of stored values? Looking at the document, I did not find a similar saying. I divided it into two cookies for storage, but there were still problems. I finally realized the possible Chinese problem (I laughed at it). solution:

Storage:

Code


   Cookie. Values. Add (truename,Httputility. urlencode(Truename ));
Cookie. Values. Add ("Nouser","");
Cookie. Expires=Datetime. maxvalue;
Cookie. Values. Add (username, username );
Cookie. Values. Add (password, password );
 

 

When reading:

 

Code


    If(Mcookie! = Null)
{
A= Httputility. urldecode(Mcookie [truename]);
Builder. appendformat (string. Format ("Current Login User: {0}", ));
}
 

 

This solves the garbled problem.

When the value is lost, what is the use of the Chinese value and the value subsequently stored? The Connection becomes a value.