Re^3: Mimicking Internet Explorer (IE) via LWP or Mechanize?

Replies are listed 'Best First'.
Re^4: Mimicking Internet Explorer (IE) via LWP or Mechanize? by pemungkah (Priest) on Aug 12, 2010 at 00:23 UTC
Yes - it's possible that if you don't need any IE-specific rendering or Javascript, and don't need to test with an ActiveX control, that straight WWW::Mechanize with `agent_alias` will suffice. That's enough to lie and say you're IE.	[reply]
Re^5: Mimicking Internet Explorer (IE) via LWP or Mechanize? by dneedles (Sexton) on Aug 12, 2010 at 14:51 UTC
Perfect! Thanks!	[reply]
Re^4: Mimicking Internet Explorer (IE) via LWP or Mechanize? by dneedles (Sexton) on Aug 12, 2010 at 00:19 UTC
I already looked and there is a lot about emulating and running javascript but nothing really on emulating IE except Win32:IE:Mechanize - which has the Frame issue. It sounds like this is new territory... I loaded IE Tab Plus on Firefox and will use Firebug to sniff the http headers and see what is triggering the site to detect IE and modify the script accordingly. Thanks anyway. Good redirects, just didn't fit the bill	[reply]
Re^5: Mimicking Internet Explorer (IE) via LWP or Mechanize? by Corion (Patriarch) on Aug 12, 2010 at 07:25 UTC
A common approach is to simply look at what goes over the wire by using a network sniffer like Wireshark. That way you are independent of what the browser program tells you (or not).	[reply]
Re^6: Mimicking Internet Explorer (IE) via LWP or Mechanize? by dneedles (Sexton) on Aug 12, 2010 at 14:53 UTC
I figure wireshark is overkill. Wouldn't Firefox 3.6.8 with IE Tab Plus and Firebug be enough? That is, the answer is in the HTTPS headers, not TCP, IP or Ethernet headers. Or is there additional traffic outside the HTTPS conversation?	[reply]