in reply to How to handle javascript

Expanding on Joost's comments, I have so far worked on page by page basis using Live HTTP headers in firefox to work out what is being sent by the browser after the java script processing.
Someday I'd like to try JavaScript::SpiderMonkey. shmem discussed it here.

non-Perl: Andy Ford

Replies are listed 'Best First'.
Re^2: How to handle javascript
by Alien (Monk) on Jan 27, 2007 at 23:06 UTC
    How can a proxy be set with those clones?
[reply]
      AFAIK those clones honour the http_proxy environment variable, e.g. on UNIX (sh, bash,...): 
      $ export http_proxy=http://proxy.example.com:3128/
$ perl myclonescript.pl

      [download]

      then the "clone" in the myclonescript.pl will connect any site through proxy.example.com.

      Or set it inside the script: 

      BEGIN {
   $ENV{http_proxy} = 'http://proxy.example.com:3128/';
}
use WWW::Mechanize
...

      [download]

      Note that the environment variable must be set before any "clone" module is loaded.

      --shmem 

      _($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
[reply]
[d/l]
[select]
      Mechanize uses LWP::UserAgent, so you can set proxies the same way.

      ($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
      =~y~b-v~a-z~s; print
[reply]

In Section Seekers of Perl Wisdom