Currently the best (the simplest) way to get site cookies in an extension is put this code in your background script: chrome.cookies.get({ url: ‘http://example.com’, name: ‘somename’ }, function (cookie) { if (cookie) { console.log(cookie.value); } else { console.log(‘Can\’t get cookie! Check the name!’); } }); So now you don’t need content script for this but … Read more
Rails has “tamper-proof” session cookies. To prevent session hash tampering, a digest is calculated from the session with a server-side secret and inserted into the end of the cookie. Just make sure you have a long secret. If you want to periodically reset all user sessions change your secret. To answer your question, if you … Read more
After much head banging, I solved this issue by setting the ‘credentials’ property of the request to ‘include’. I was under the impression that this only controlled the sending of cookies to the server on fetch requests, but apparently, at least in the implementation I am using, if not set it also means that cookies … Read more
The session cookie is per-process not per window. So even if you selected New Window you’d still get the same session id. This behavior makes sense. You wouldn’t want a user to re-sign in each time they opened a new window while browsing your site. I’m not aware off hand of any real way around … Read more
The solution would be to set SESSION_COOKIE_DOMAIN = ‘.example.com’ and rename the session cookie name, e.g. SESSION_COOKIE_NAME = ‘examplesessionid’ on the Django instance that is driving the two subdomains. The two sites will use the renamed cookie with a global scope and not interfere with the other Django instances, using the default ‘sessionid’ cookie on … Read more
You could use the pm.environment.set(‘my_cookie’, pm.cookies.get(‘JSESSIONID’)) function in the Tests tab and store it as an environment variable. This can then be used in the next Request Body (If chaining them together) or in any Request Body or Request Header by referencing the value using the {{my_cookie}} syntax. A very similar issue can be found … Read more
It turned out that the root cause was the Ajax call. The problematic flow was 1) OAuth cookie got expired after some time 2) Expiration normally causes redirection the page to login.microsoft.com to refresh the cookie. In this step OAuth framework adds new nonce cookie to the response (every time)! 3) But Ajax doesn’t handle … Read more
As you can read in this topic: You combine the use jQuery.cookie plugin and JSON and solve your problem. When you want to store an array, you create an array in JS and use JSON.stringify to transform it into an string and stored with $.cookie(‘name’, ‘array_string’) var myAry = [1, 2, 3]; $.cookie(‘name’, JSON.stringify(myAry)); When … Read more