Re: Slow WWW::Mechanize->get

Ank_:

The only theory I have is that the site is looking at the user agent string to do some things, and when it doesn't contain a 'mainstream' agent string, their site may be doing something to make it slower. To test the theory, try setting up a different agent string and see if it replies faster.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

Comment on Re: Slow WWW::Mechanize->get

Replies are listed 'Best First'.
Re^2: Slow WWW::Mechanize->get by Anonymous Monk on Jan 26, 2013 at 01:40 UTC
Dear roboticus, I just recognized the right question to ask: How can I print/see/dump/compare WWW::Mechanize's and Firefox's user agent strings set to the site.	[reply]
Re^3: Slow WWW::Mechanize->get by roboticus (Chancellor) on Jan 26, 2013 at 02:17 UTC
From the docs: `$mech->agent_alias('Windows Mozilla')` is probably sufficient. You can use `$mech->known_agent_aliases()` to get a list of the agent aliases built into WWW::Mechanize. ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply] [d/l] [select]
Re^4: Slow WWW::Mechanize->get by AnK_ (Initiate) on Jan 26, 2013 at 02:26 UTC
Oh, this i tried... And more complex variations too, like: verify_hostname => 0,noproxy => 0,cookie_jar=>{'ASP.NET_SessionId'=>'ihbh5neysr4cxybrgsskbm45'},agent=>"Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0" and other possible parameters.	[reply]
Re^3: Slow WWW::Mechanize->get by Anonymous Monk on Jan 26, 2013 at 01:49 UTC
read the docs :) ->res->headers->as_string	[reply]
Re^4: Slow WWW::Mechanize->get by AnK_ (Initiate) on Jan 26, 2013 at 02:11 UTC
Thanks. However to understand the difference between WWW::Mechanize and Firefox i need the headers before get( $start_page ). The $mech->res->headers->as_string is not defined there. Sorry, if i misunderstood your reply.	[reply]
Re^2: Slow WWW::Mechanize->get by Anonymous Monk on Jan 26, 2013 at 01:11 UTC
Thanks, roboticus, will do ...	[reply]