BTW, I've also checked whether pre-3.2 NF versions (3.2 has an encrypted cookie file - this is, security- and privacy-wise, certainly welcome in 3.2 and, in this respect, even better compared to the user-readable cookie format used by most other browsers, including even the desktop-based Internet Explorer - unlike its predecessors; therefore, it can't be read/edited) store cookies that are no longer valid in their
NF3.cok file in the home directory.
If they stored them, then, just a simple modification could suffice with a simple text editor. The format of the cookie records in NF is as follows:
Code:
server path 1 expires cookie-name cookie-value
where
expires is a simple string formatted in conformance with RFC 1123 (see the
http://www.w3.org/Protocols/rfc2616/....html#sec3.3.1 on this). It can be freely edited (as with other parts of this file).
In this case, it doesn't help, though - expired cookies aren't stored.
Bottom line: The only way to make NF work with sites returning cookies that are valid for less than an hour is setting back the PDA clock with at least one hour before visiting the site.