I have a script that walks through some sites of ours and buys products. LWP::UserAgent is used along with the other expected modules: HTTP::Request, HTTP::Response, HTTP::Headers, etc.
The problem is that periodically I get those self-generated 500 errors from the HTTP protocol layer. These are almost always EOF before status line seen.
Is this something others have hit? If so I'd be interested in hearing how you handled them. Right now it's too complicated for me to try and get the user back in without knowing the exact chain of responses, so I just bomb out and throw these to an exception pile. Ideally I'd like to recover and continue, but without a response that's not possible. I'm thinking maybe there's some socket level retry that's warranted or something, but I don't see how to do that at the LWP level.
In reply to LWP::UserAgent socket errors by steves
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |