chrome-cookies-secure's Introduction

chrome-cookies-secure

Extract encrypted Google Chrome cookies for a url on Mac OS X or Linux

Installation

npm install chrome-cookies-secure

API

getCookies(url[,format],callback)

url should be a fully qualified url, e.g. http://www.example.com/path/

format is optional and can be one of the following values:

format	description
curl	Netscape HTTP Cookie File contents usable by curl and wget
jar	cookie jar compatible with request
set-cookie	Array of Set-Cookie header values
header	`cookie` header string, similar to what a browser would send
object	(default) Object where key is the cookie name and value is the cookie value. These are written in order so it's possible that duplicate cookie names will be overriden by later values

If format is not specified, object will be used as the format by default.

Cookie order tries to follow RFC 6265 - Section 5.4, step 2 as best as possible.

Examples

basic usage

var chrome = require('chrome-cookies-secure');
chrome.getCookies('http://www.example.com/path/', function(err, cookies) {
	console.log(cookies);
});

jar used with request

var request = require('request');
var chrome = require('chrome-cookies-secure');

chrome.getCookies('http://www.example.com/', 'jar', function(err, jar) {
	request({url: 'http://www.example.com/', jar: jar}, function (err, response, body) {
		console.log(body);
	});
});

Limitations

On OS X, this module requires Keychain Access to read the Google Chrome encryption key. The first time you use it, it will popup this dialog:

The SQLite database that Google Chrome stores its cookies is only persisted to every 30 seconds or so, so this can explain while you'll see a delay between which cookies your browser has access to and this module.