On 1/18/12 2:47 PM, NoOp wrote: > On 01/16/2012 02:49 PM, David E. Ross wrote: >> On 1/16/12 1:47 PM, Ray_Net wrote: > ... >>> Is it posssible to modify the cookie in such a way that the expiration >>> date will be 1/1/2100 ? >>> >> >> Locate the cookie in the cookies.sqlite database. Locate within the >> cookie the expiration date; RFC 6265 at >> <http://www.rfc-editor.org/rfc/rfc6265.txt> should be useful for that. >> Edit it with a hex editor. > > Instead while on a browser page: Tools|SQLite Manager > Open cookies.sqlite & modify the date there. For example I allowed a > cookie to be set (I normally delete when closing the session) and the > expiry (INTEGER) is: 1390075201 > That decodes as: > Sat Jan 18 12:00:01 PST 2014 > > $ date -d @1390075201 > Sat Jan 18 12:00:01 PST 2014 > > If you wish to modify that to 2100 then you'll need to work out the > seconds (seconds since 1970-01-01 00:00:00 UTC). However, you'll find > that 2100 gives: > $ date +%s -d 2100-01-18t12:00 > date: invalid date `2100-01-18t12:00' > > so change to something reasonable, like 2030: > $ date +%s -d "2030-01-18 12:00Z" > 1894968000 > $ date -d @1894968000 > Fri Jan 18 04:00:00 PST 2030 > > So now change the expiry 1390075201 to 1894968000 and the cookie won't > expire until Jan 18, 2030. >
When I select Tools on the SeaMonkey menu bar, I do not see any SQLite Manager, not even on any of the submenus. Did you install SQLite Manager on your system? If so, what version? -- David E. Ross <http://www.rossde.com/>. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
