If it is indeed a login problem. The issue is that the OP is probably not keeping up with cookies.
Since HTTP is a stateless protocol, the server has no concept of a login. The application may have a session concept which is normally tracked with cookies. This is why I suspect the problem is cookie related. As I recall, LWP::UserAgent has a feature for using HTTP::Cookies to track a cookie jar that handles this issue.
In reply to Re^2: HTTP Post read response , Post again
by gwadej
in thread HTTP Post read response , Post again
by perljunkie
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |