AnyEvent-HTTP
view release on metacpan or search on metacpan
function from time to time.
A cookie jar is initially an empty hash-reference that is managed by this
module. Its format is subject to change, but currently it is as follows:
The key C<version> has to contain C<2>, otherwise the hash gets
cleared. All other keys are hostnames or IP addresses pointing to
hash-references. The key for these inner hash references is the
server path for which this cookie is meant, and the values are again
hash-references. Each key of those hash-references is a cookie name, and
the value, you guessed it, is another hash-reference, this time with the
key-value pairs from the cookie, except for C<expires> and C<max-age>,
which have been replaced by a C<_expires> key that contains the cookie
expiry timestamp. Session cookies are indicated by not having an
C<_expires> key.
Here is an example of a cookie jar with a single cookie, so you have a
chance of understanding the above paragraph:
{
version => 2,
A cookie jar is initially an empty hash-reference that is managed by
this module. Its format is subject to change, but currently it is as
follows:
The key "version" has to contain 2, otherwise the hash gets cleared.
All other keys are hostnames or IP addresses pointing to
hash-references. The key for these inner hash references is the
server path for which this cookie is meant, and the values are again
hash-references. Each key of those hash-references is a cookie name,
and the value, you guessed it, is another hash-reference, this time
with the key-value pairs from the cookie, except for "expires" and
"max-age", which have been replaced by a "_expires" key that
contains the cookie expiry timestamp. Session cookies are indicated
by not having an "_expires" key.
Here is an example of a cookie jar with a single cookie, so you have
a chance of understanding the above paragraph:
{
version => 2,
( run in 0.749 second using v1.01-cache-2.11-cpan-702932259ff )