This is ‘new’ functionality in IE8! Checkj out the IE8 blog below to read about it. http://blogs.msdn.com/askie/archive/2009/03/09/opening-a-new-tab-may-launch-a-new-process-with-internet-explorer-8-0.aspx IE8 can use multiple processes for handling an x number of IE windows. When you cross a process space, you loose your cookies (Asp.Net session ID seems to be retained over this process boundry). I personally think it’s … Read more
You can use -b to specify a cookie file to read the cookies from as well. In many situations using -c and -b to the same file is what you want: curl -b cookies.txt -c cookies.txt http://example.com Further Using only -c will make curl start with no cookies but still parse and understand cookies and … Read more
You can build a cookie-proxy by creating a Flash application and use Shared Objects (SO = Flash cookies) to store data. Any Browsers with Flash installed could retrieve the informations stored in the SO. But, it’s an ugly workaround. Just don’t share cookies… and find another way to build your website/app.
Understanding Cookies Cookies are given to a browser by the server. The browser reveals the cookies as applicable only to the domain that provided the cookie in the first place. The data in the cookie allows the server to continue a conversation, so to speak. Without the cookie, the server considers the browser a first-time … Read more
No more than 50 cookies per domain, with a maximum of 4 KB per cookie (or even 4 KB in total, see Iain’s answer). On IE 6 it used to be 20 cookies per domain. Generally it’s recommended to preserve state on the server, and use cookies only for session tracking. They’re sent along with … Read more
The cookie specs require two names and a dot between, so your cookiedomain cannot be “localhost”. Here’s how I solved it: Add this to your %WINDIR%\System32\drivers\etc\hosts file: 127.0.0.1 dev.livesite.com When developing you use http://dev.livesite.com instead of http://localhost Use “.livesite.com” as cookiedomain (with a dot in the beginning) when creating the cookie. Modern browsers doesn’t require … Read more
So the iFrame isn’t actually setting the u cookie for the runwithfriends.appspot.com domain. What Facebook does is it creates a form, <form action=”runwithfriends.appspot.com/…” target=”name_of_iframe” method=”POST”> and uses javascript to submit the form on page load. Since the form’s target is the iframe, it doesn’t reload the page… it just loads the iframe with the POST’s … Read more
I have managed to solve this issue with the help of Vasiliy Baranov from Oracle. Vasiliy wrote to me: Try putting the cookie into java.net.CookieHandler.getDefault() after the WebView is instantiated for the first time and before the call to WebEngine.load, e.g. as follows: WebView webView = new WebView(); URI uri = URI.create(“http://mysite.com”); Map<String, List<String>> headers … Read more
The leading dot means that the cookie is valid for subdomains as well; nevertheless recent HTTP specifications (RFC 6265) changed this rule so modern browsers should not care about the leading dot. The dot may be needed by old browser implementing the deprecated RFC 2109. RFC 6265 section 4.1.2.3 For example, if the value of … Read more
It looks like you hit a Safari bug here; you are redirecting any visiting browser to /entry while setting the cookie at the same time, and Safari is ignoring the Set-Cookie header when encountering the 302 HTTP status: $ curl -so /dev/null -D – http://4much.schnickschnack.info/ HTTP/1.1 302 Moved Temporarily Server: nginx/0.7.61 Date: Sun, 19 Jul … Read more