Re^4: Using WWW::Scripter with NTLM authentication

in reply to Re^3: Using WWW::Scripter with NTLM authentication
in thread Using WWW::Scripter with NTLM authentication

I'm not explicitly cloning, it happens when WWW::Scripter starts reading referenced JavaScript files (when using the JavaScript plugin). The oroginal HTML document loads fine, I get the NTLM authorisation errors when the .js files are being read.

Cheers,
LB.

Comment on Re^4: Using WWW::Scripter with NTLM authentication

Replies are listed 'Best First'.
Re^5: Using WWW::Scripter with NTLM authentication by rowdog (Curate) on Feb 04, 2011 at 10:41 UTC
Hrm, I hadn't realized that WWW::Mechanize::FAQ says that Mech keeps a history of every page, and the state it was in. It actually keeps a clone of the full Mech object at every step along the way. So, there's a clone for each step. I'm kind of in over my head here but I don't see anything wrong with your workaround, as long as you're not sending requests from a bunch of different threads or something silly like that.	[reply]

Replies are listed 'Best First'.

Re^5: Using WWW::Scripter with NTLM authentication
by rowdog (Curate) on Feb 04, 2011 at 10:41 UTC

Hrm, I hadn't realized that WWW::Mechanize::FAQ says that

Mech keeps a history of every page, and the state it was in. It actually keeps a clone of the full Mech object at every step along the way.

So, there's a clone for each step. I'm kind of in over my head here but I don't see anything wrong with your workaround, as long as you're not sending requests from a bunch of different threads or something silly like that.

[reply]

In Section Seekers of Perl Wisdom