IE JavaScript cookie path setting bug

a cookie was set up in the project and was successfully tested under Firefox. There was a problem with the IE test, and the location found to be a problem with the path to JavaScript setting cookies. The cookie under IE is set to the path of the URL, and if the cookie value is scoped to the current URL, then the JavaScript under IE cannot get the cookie value set.

Look at the following demo code, note the following path differences :

2. var cookie_name = "name";
4. var cookie_value = "value";
6. expires = new Date ();
8. Expires.settime (Expires.gettime () + 86400 * 1000);
12. // bug Document.cookie cannot read to Cookie_name value
14. Document.cookie = Cookie_name + "=" + encodeuricomponent (cookie_value)
16. + "; expires= " + expires.togmtstring () + "; path="
18. + Window.location.pathname;
20. //Normal
22. Document.cookie = Cookie_name + "=" + encodeuricomponent (cookie_value)
24. + "; expires= " + expires.togmtstring () + "; path=/test/";
26. //Normal
28. Document.cookie = "cookie_name=" + encodeuricomponent (cookie_value)
30. + "; expires= " + expires.togmtstring () + "; path=/";

Results: The cookie value is only valid for the current page. I don't know now.

Alternative, Code:

2. //ie Cookie Bug substitution scheme
4. var cookie_path = Window.location.pathname;
6. var cookie_name = encodeURIComponent (cookie_path.substring (Cookie_path
8. . LastIndexOf ('/') + 1));
10. Cookie_path = cookie_path.substring (0, Cookie_path.lastindexof ('/') + 1);
12. var cookie_value = "value";
14. expires = new Date ();
16. Expires.settime (Expires.gettime () + 86400 * 1000);
20. Document.cookie = Cookie_name + "=" + encodeuricomponent (cookie_value)
22. + "; expires= " + expires.togmtstring () + "; Path= " + Cookie_path;

The alternative is to make a cookie name based on the URL file name of each page, valid within the current page path.
such as: URL equals/test/test.html
The cookie is named test.html and the valid path is/test/
This can also be done with the same JS deployment on each page can read to the current URL only valid cookie value. The price is that when users access many pages in the same level directory, the cookie value increases. As a result, each HTTP request under the current path has a long cookie, which directly causes the server to receive the header length of the client request, and the server burden increases as the traffic grows. And according to the definition of RFC 2109 cookie also has the length and number of limits, ie the maximum allowable cookie length is 4096 bytes, allow 50 cookie name-value pairs. If you want to break the limit of 50 name-value pairs, you can save more cookie variables in a single name-value using a cookie dictionary.

Reference from: http://conkeyn.iteye.com/blog/423549

IE JavaScript cookie path setting bug