in reply to Re: WWW::Mechanize fetch differs from firefox browser result (was Re: WWW::Mechanize or WWW::Selenium with javascript redirect)
in thread WWW::Mechanize or WWW::Selenium with javascript redirect

Seriously, there is no need to use Selenium or IE. If you use a logging proxy or the Firefox LiveHTTPHeaders extension, you will see exactly what the browser sends to the server, and then you just have to make your script send the same thing. No actual execution of JavaScript is required, since the server has no way to tell if you ran any client-side code or not.
  • Comment on Re^2: WWW::Mechanize fetch differs from firefox browser result (was Re: WWW::Mechanize or WWW::Selenium with javascript redirect)

Replies are listed 'Best First'.
Re^3: WWW::Mechanize fetch differs from firefox browser result (was Re: WWW::Mechanize or WWW::Selenium with javascript redirect)
by tphyahoo (Vicar) on Jan 19, 2007 at 09:38 UTC
    I am going to try out LiveHTTPHeaders; thanks for that suggestion. I think partly my difficulties are just due to my general ignorance of javascript.

    However, I still see value value in figuring out a more general way to do it, that susses out any popup windows and checks them, regardless of how they were generated. If I can get that to work, I won't have to change the code even if something changes in the javascript.

[reply]
      I'm also trying LiveHTTPHeaders, the output is a little confusing though.

      Question:

      1. Many HTTP lines are passed.
      2. Do I need to create a new mech object for each "HTTP" that I captured?
      Has anyone had any success yet?
[reply]
        So you need to read a basic HTTP/CGI tutorial
[reply]

In Section Seekers of Perl Wisdom