Quote:
Originally Posted by kovidgoyal
javascript can set arbitrary headers, not just cookies. So you have to resort to exaing the actual HTTP requests to see the difference.
|
yeah but i assumed the cookie once set and able to crawl would work well same way it would once set in a browser but different session. in this case loading teh whole cookie file as MozillaCookeJar doesn't seem to work with mechanize - either mechanize not reading properly or there's some other behaviour going on to fingerprint the login as mechanical.