I am trying to determine why the following commands to WWW::Mechanize::Shell result as they do:
[EMAIL PROTECTED] trwww]$ perl -MWWW::Mechanize::Shell -e 'shell' >get https://www.setsivr.odjfs.state.oh.us/Login.asp Retrieving https://www.setsivr.odjfs.state.oh.us/Login.asp(200) https://www.setsivr.odjfs.state.oh.us/cookieerror.htm> The server appears to check requests for an asp session cookie. If one is not set, the servers response includes a Set-Cookie header and a Location: header set to /cookiecheck.asp. If the request to cookiecheck.asp does not have the cookie in the header, the client is then redirected to cookieerror.htm. If /cookiecheck.asp finds the cookie, it appears to redirect the client to the initial request, whose URI mustve been stored in the session. Why does WWW::Mechanize get directed to cookieerror.htm? I've posted this question before with no responses. I have done some deeper digging, but still with no success. I am hoping someone would be willing to assist this time. The above procedure works with all the popular graphical browsers I have used. Lynx does NOT produce desired results, landing on cookieerror.htm like WWW::Mechanize does. I tried to establish a session with the server using IO::Socket::SSL using the example from the POD. You can see the code at the following URI: http://waveright.homeip.net/~trwww/code/iosocketsslclient.txt The first attempt sends a single line request to /Login.asp. The code then extracts the cookie and makes a two line request to /cookiecheck.asp. The response to this request is to redirect to cookieerror.htm. The second attempt uses the HTTP headers I scraped from the "Live HTTP Headers" module available with Mozilla. The requests appear to be successful, but the reads hang. Please help with this possible bug which I am sure has turned away more than one user from libwww-perl. Thank you, Todd W. _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!
