Try something newer: HTTP::CookieJar::LWP

That has no documentation at all! It doesn't even say what methods it has. It seems to expect you to go through the LWP source code and find the calls listed in the HTTP::Cookie documentation.

No, it says:

SYNOPSIS

use LWP::UserAgent;
use HTTP::CookieJar::LWP;
 
my $ua = LWP::UserAgent->new(
  cookie_jar => HTTP::CookieJar::LWP->new
);
[download]

and then it says

DESCRIPTION

This module is an experimental adapter to make HTTP::CookieJar work wi
+th LWP.
[download]

So you go read the docs for HTTP::CookieJar and find that they are comprehensive. You may also need to read some of the docs for LWP::UserAgent.

Here is a simple example:

#! perl
use strict;
use warnings;
use feature qw/ say /;
use Data::Dumper;
use LWP::UserAgent;
use HTTP::CookieJar::LWP;

my $protocol = 'http://';
my $domain   = 'www.foobar.com';
my $path     = '/baz';
my $page     = '/qux.html';
my $url      = join '', $protocol, $domain, $path, $page;

my $file     = 'cookies.txt';

## Only here for demo. You would have a cookie file
## made somewhere else, or if not you would pass the 
## values directly to HTTP::CookieJar::LWP::add()
open( my $write_handle, '>', $file ) or die "open: $!\n";
print $write_handle "Secret_Number=42; Max-Age=300; Domain=$domain; Pa
+th=$path\n";
close $write_handle or die "close: $!\n";

my $ua = LWP::UserAgent->new(
    cookie_jar => HTTP::CookieJar::LWP->new()
);

open( my $read_handle, '<', $file ) or die "open: $!\n";
foreach my $cookie ( <$read_handle> ) { 
  chomp $cookie;
  $ua->cookie_jar->add( $url, $cookie );
}

say $ua->cookie_jar->cookie_header( $url );
say Dumper $ua->cookie_jar->cookies_for( $url );

__END__
[download]

Output:

[00:04][nick:~/monks]$ perl 1139766.pl
Secret_Number=42
$VAR1 = {
          'name' => 'Secret_Number',
          'domain' => 'www.foobar.com',
          'expires' => 1440486562,
          'value' => '42',
          'path' => '/baz',
          'last_access_time' => 1440486262,
          'creation_time' => 1440486262
        };
[download]

Now you just GET the URL with LWP::UserAgent in the normal way, and the cookie goes right along in the headers.

Hope this helps!

The way forward always starts with a minimal test.

Looking at the source code for HTTP::Cookies,

$version defaults to 0, but in other code, it defaults to 1 if $discard or $secure are set, but only if it hasn't already defaulted to zero?

$path_spec is optional?, and adds a "\$Path="$path" line to the HTTP header. I don't know what this does.

It appears that setting $discard causes the cookie to be deleted at some time; perhaps end of session?

It is not clear at all how $port works, but it seems to be optional

Also, googling shows other people have asked what the documentation means, and the module's creator replied by saying he didn't see how it could be made any clearer.

Thanks for the module, but that part of the documentation could be made clearer.

How do you create a cookie to use with LWP::UserAgent?

I'm curious, aren't cookies something created by the website you're visiting?

Also, googling shows other people have asked what the documentation means, and the module's creator replied by saying he didn't see how it could be made any clearer.

Do you have a link?

There is an example of generating a netscape cookie file in https://metacpan.org/source/GAAS/HTTP-Cookies-6.01/t/cookies.t, it also includes adding cookies to a cookie jar

I think what the author might be talking saying is check the RFC for the the meaning of those values

For example https://en.wikipedia.org/wiki/Http_cookie#Cookie_attributes

RFC 6265 - HTTP State Management Mechanism

Comment / CommentURL explained in RFC 2965 - HTTP State Management Mechanism

Or even https://metacpan.org/pod/CGI#HTTP-COOKIES

and path_spec A Boolean value indicating if the cookie is valid for the specific URL path or all the URLs in the domain. The path is used if true; otherwise, the cookie is valid for the entire domain.

http://grep.cpan.me/?q=path_spec&page=2 -> https://metacpan.org/pod/HTTP::WebTest#path_spec-PATH_SPEC

That covers everything right?