<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Browser cookie restriction research</title>
	<atom:link href="http://ajaxian.com/archives/browser-cookie-restriction-research/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/browser-cookie-restriction-research</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: briandunnington</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-265664</link>
		<dc:creator>briandunnington</dc:creator>
		<pubDate>Fri, 04 Jul 2008 19:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-265664</guid>
		<description>although opera will accept up to 30 cookies, and the max size is 4096, there is also a total-size-for-all-cookies-per-domain limit of 5000 bytes. so if you use a really large cookie, you may only be able to store one cookie:
http://my.opera.com/gorme/blog/show.dml/13293

you can also use this online test tool to test your cookie limits:
http://krijnhoetmer.nl/stuff/javascript/maximum-cookies/

if you use very large values for the cookie value, you can see that opera starts to discard many more cookies.</description>
		<content:encoded><![CDATA[<p>although opera will accept up to 30 cookies, and the max size is 4096, there is also a total-size-for-all-cookies-per-domain limit of 5000 bytes. so if you use a really large cookie, you may only be able to store one cookie:<br />
<a href="http://my.opera.com/gorme/blog/show.dml/13293" rel="nofollow">http://my.opera.com/gorme/blog/show.dml/13293</a></p>
<p>you can also use this online test tool to test your cookie limits:<br />
<a href="http://krijnhoetmer.nl/stuff/javascript/maximum-cookies/" rel="nofollow">http://krijnhoetmer.nl/stuff/javascript/maximum-cookies/</a></p>
<p>if you use very large values for the cookie value, you can see that opera starts to discard many more cookies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joeri</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263985</link>
		<dc:creator>Joeri</dc:creator>
		<pubDate>Wed, 21 May 2008 11:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263985</guid>
		<description>For anyone interested, this is the knowledge base article for the IE bump from 20 to 50 cookies per domain:
http://support.microsoft.com/kb/941495</description>
		<content:encoded><![CDATA[<p>For anyone interested, this is the knowledge base article for the IE bump from 20 to 50 cookies per domain:<br />
<a href="http://support.microsoft.com/kb/941495" rel="nofollow">http://support.microsoft.com/kb/941495</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jclawson</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263976</link>
		<dc:creator>jclawson</dc:creator>
		<pubDate>Tue, 20 May 2008 18:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263976</guid>
		<description>Ok, more specifically... Even though you can store 4095 characters in a cookie, Apache, by default only accepts a header with a length of 8190.  This includes the cookie names, equals sign, value, and all headers sent in the request (including the GET parameters).

We were running into this issue using ExtJS and the default cookie state provider.  You can read more about this here: http://www.jasonclawson.com/2008/05/20/ext-21-state-managment-issues-dont-use-it/</description>
		<content:encoded><![CDATA[<p>Ok, more specifically&#8230; Even though you can store 4095 characters in a cookie, Apache, by default only accepts a header with a length of 8190.  This includes the cookie names, equals sign, value, and all headers sent in the request (including the GET parameters).</p>
<p>We were running into this issue using ExtJS and the default cookie state provider.  You can read more about this here: <a href="http://www.jasonclawson.com/2008/05/20/ext-21-state-managment-issues-dont-use-it/" rel="nofollow">http://www.jasonclawson.com/2008/05/20/ext-21-state-managment-issues-dont-use-it/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263975</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Tue, 20 May 2008 17:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263975</guid>
		<description>&gt;&gt;Interesting research but iâ€™ve never understood why anyone would set more than 2 cookies for a user and why you would need 4095 characters is beyond me.

Well, I have a case in a personal financial application where I do a lot of statistics. If I save the results into a cookie, the user bypasses anywhere from 10 seconds to 2 minutes of processing. The resultant data is a few kilobytes. If the cookie is cleared, no problem, but the user has to sit through the processing again.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;Interesting research but iâ€™ve never understood why anyone would set more than 2 cookies for a user and why you would need 4095 characters is beyond me.</p>
<p>Well, I have a case in a personal financial application where I do a lot of statistics. If I save the results into a cookie, the user bypasses anywhere from 10 seconds to 2 minutes of processing. The resultant data is a few kilobytes. If the cookie is cleared, no problem, but the user has to sit through the processing again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mojave</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263973</link>
		<dc:creator>mojave</dc:creator>
		<pubDate>Tue, 20 May 2008 17:19:20 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263973</guid>
		<description>Interesting research but i&#039;ve never understood why anyone would set more than 2 cookies for a user and why you would need 4095 characters is beyond me.  I realize Rails has done this insanely stupid thing where it stores session data in cookies, but that&#039;s about as intelligent as using lighttpd and fastcgi.  &quot;Let&#039;s send data to the sever just to store it back in the client oh and while we&#039;re at it we&#039;ll send it with every freaking request.&quot;  Thanks I&#039;ll stick to storing state in memcache or a hash table.</description>
		<content:encoded><![CDATA[<p>Interesting research but i&#8217;ve never understood why anyone would set more than 2 cookies for a user and why you would need 4095 characters is beyond me.  I realize Rails has done this insanely stupid thing where it stores session data in cookies, but that&#8217;s about as intelligent as using lighttpd and fastcgi.  &#8220;Let&#8217;s send data to the sever just to store it back in the client oh and while we&#8217;re at it we&#8217;ll send it with every freaking request.&#8221;  Thanks I&#8217;ll stick to storing state in memcache or a hash table.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jclawson</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263969</link>
		<dc:creator>jclawson</dc:creator>
		<pubDate>Tue, 20 May 2008 16:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263969</guid>
		<description>I recently encountered a problem where firefox would fail to make the page request if there were a large number of cookies and the GET request was beyond a certain length.  Clearing the cookies fixed the issue.  I will create a demo and post it on my blog later.</description>
		<content:encoded><![CDATA[<p>I recently encountered a problem where firefox would fail to make the page request if there were a large number of cookies and the GET request was beyond a certain length.  Clearing the cookies fixed the issue.  I will create a demo and post it on my blog later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MaratDenenberg</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263967</link>
		<dc:creator>MaratDenenberg</dc:creator>
		<pubDate>Tue, 20 May 2008 16:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263967</guid>
		<description>You can get around the cookie limit by serializing your data, for instance in JSON format. Just be mindful of the character limit. You can write a small class to automate everything, like a cookie manager, that will make sure you don&#039;t go over the limit.</description>
		<content:encoded><![CDATA[<p>You can get around the cookie limit by serializing your data, for instance in JSON format. Just be mindful of the character limit. You can write a small class to automate everything, like a cookie manager, that will make sure you don&#8217;t go over the limit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilazarte</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263966</link>
		<dc:creator>ilazarte</dc:creator>
		<pubDate>Tue, 20 May 2008 16:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263966</guid>
		<description>He also could&#039;ve checked wikipedia to read the same thing :)</description>
		<content:encoded><![CDATA[<p>He also could&#8217;ve checked wikipedia to read the same thing :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nosredna</title>
		<link>http://ajaxian.com/archives/browser-cookie-restriction-research/comment-page-1#comment-263961</link>
		<dc:creator>Nosredna</dc:creator>
		<pubDate>Tue, 20 May 2008 14:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/browser-cookie-restriction-research#comment-263961</guid>
		<description>This can be tricky stuff when you consider dependencies. I especially don&#039;t like what Firefox appears to be doing. I&#039;d like to know why they aren&#039;t using LRU.

If you can&#039;t manage to store a bunch of grouped data in a cookie and have to split it up into different cookies, you have to make sure that all the data is still extant before launch into code that assumes all the data is there. This can bite you if you aren&#039;t thinking clearly about it every time you use cookies.

It&#039;s as if a random chunk of your variable space can disappear at any time. Setting up unit tests and QA for this stuff is tricky.

If you can keep all your cookie data in one 4000 character chunk, great. If you can&#039;t, it seems to me you really want to be careful not to pass 20 cookies, just in case you run into an old browser. (Anyone know more about when IE switched from 20 to 50?)</description>
		<content:encoded><![CDATA[<p>This can be tricky stuff when you consider dependencies. I especially don&#8217;t like what Firefox appears to be doing. I&#8217;d like to know why they aren&#8217;t using LRU.</p>
<p>If you can&#8217;t manage to store a bunch of grouped data in a cookie and have to split it up into different cookies, you have to make sure that all the data is still extant before launch into code that assumes all the data is there. This can bite you if you aren&#8217;t thinking clearly about it every time you use cookies.</p>
<p>It&#8217;s as if a random chunk of your variable space can disappear at any time. Setting up unit tests and QA for this stuff is tricky.</p>
<p>If you can keep all your cookie data in one 4000 character chunk, great. If you can&#8217;t, it seems to me you really want to be careful not to pass 20 cookies, just in case you run into an old browser. (Anyone know more about when IE switched from 20 to 50?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

