in reply to Re^6: WWW::Mechanize and fooling server for javascript
in thread WWW::Mechanize and fooling server for javascript

This is why I mentioned the various methods of tracing what your browser sends over the wire. If you don't know how HTTP, HTML and browsers interact, watching the whole thing in action (or in slow motion replay via the logs) can be quite educating.

Yes,you will need to request all separately linked things separately. As you will be replicating the stuff a browser sends, the server has no method of discerning between your script and a browser. How the serser stitches together all the separate requests into a whole session is up to the server. Cookies are a common method, but you will likely find when you look at the traffic that much of the traffic is static anyway. So, go look at what goes over the wire.

  • Comment on Re^7: WWW::Mechanize and fooling server for javascript

Replies are listed 'Best First'.
Re^8: WWW::Mechanize and fooling server for javascript
by gw1500se (Beadle) on Aug 01, 2007 at 11:33 UTC
    Thanks but again knowing what goes over the wire is not my problem. What I'm struggling with is on the perl side which is why I'm here. I KNOW what is coming over the wire, the problem is how to extract that with Mech or LWP.

    It appears to me that Mech ignores <script ... src="some link"> tags. I can see no way to get that source as that tag does not even show up with a "get".
      I guess I have it. I can now see the javascript tag so I can extract the 'src' parameter then do another 'get' on that. I have what I need to move on. Thanks.