Hi, I am writing about 20 cookies using a common method through java on one of the pages and trying to read them on next page. In Internet Explorer one of the cookie is not available. There is no place in between where the cookie is getting overwritten / deleted. Also the code works perfect in mozilla but not in Explorer. The strange thins is everytime the same cookie is not available. Can anyone please suggest what could be going wrong.
when you say 'next page', is this in the same window or are you opening a new window? There is a known issue with some versions of IE where sessions can get lost when opening a new window, and I presume cookies are the same.
Microsoft Internet Explorer complies with the following RFC 2109 recommended minimum limitations: •at least 300 cookies •at least 4096 bytes per cookie (as measured by the size of the characters that comprise the cookie non-terminal in the syntax description of the Set-Cookie header) •at least 20 cookies per unique host or domain name
Is it documented somewhere that there can be only 20 cookies in IE ?
William was so kind to include a link to the relevant documentation in his post.
Also the cookies that get lost are not the last ones in the hashmap.
Since it is not guaranteed that more than 20 will be supported, trying to guess which ones beyond that will be ignored is just idle speculation.
I'd question any design that relies on this many cookies to begin with. Can you tell us why you think that's necessary?
Ping & DNS - updated with new look and Ping home screen widget
Joined: May 04, 2007
The content for the page is to be picked up from Documentum and since that reads cookies all the data had to be transferred from request/hidden fields to the Cookies.
Joined: Feb 26, 2007
And what if the cookie is not supported. In that case will your application not work.
And more over in the case of cookies, you never know the way the cookies are sent : in which order. So even if the end cookies in the hasmap are not missing, quiet possible that they are going in the starting of the sequence. So you never know the exact sequence.
I believe that an applications main feature should not be built around cookies.Not , at least for a completely web based applications , where you do not know the settings of the browser that the client might be using.But there are few other stuffs to look at for tracking client sessions.
But its fine for web based products as products will have a system requirement where the vendor might say that for running this application cookies must be allowed.