Implementation of second-level domain names or cross-domain cookies sharing

Note:
1. When you have a cookie group (or cookie dictionary) that uses the domain attribute to specify a domain name, when you modify or add new members to the group, you must add resonse after the operation. cookies (cookiename ). domain attribute.
2. If you do not need to modify the cookie Group of the domain, use response. Cookies ("cookietext") = cookievalue to create a new cookie. For each independent response. Cookies ("cookietext"), all data is written in one time regardless of the dictionary. If you need to write data multiple times, change to response. Cookies ("cookietext "). This is important.
3. response. Cookies ("cookiename"). Secure = false. The secure attribute must be false.
Example:
Response. Cookies ("uto") ("utorname") = utorname
Response. Cookies ("uto") ("utorpwd") = utorpwd
Response. Cookies ("uto"). Domain = "utoper.com"
Response. Cookies ("uto"). Secure = false
4, ie for. cn short domain support has a major bug, no way to write cookies, Someone tested: http://blog.csdn.net/xssh913913/archive/2007/08/04/1725882.aspx solution:
For example, for h5.cn domain names, all subdomain names in h5.cn write cookies to the h5.cn domain no matter which subdomain name receives the information. Do not set the domain name when writing, that is, these two statements are not required.
Response. Cookies ("user"). Domain = "h5.cn"
Response. Cookies ("user"). Secure = false
In this way, cookies can be called by any other subdomain name.