I have a similar (exasperating ;) ) problem while using LWP UserAgent to get a Status page from a LinkSys BEFSR41 (from LAN side peer client).

AFTER full 4673 bytes of Status HTML is received from server, LWP sends a redundant terminal request that provokes a 500 "Can't read entity body" response AND wipes out the $response->content.

Same thing happens if I use a filename method, except that file contains 4673 expected response bytes but $response->content is empty.

LWP::DebugFile Log:-

# LWP::DebugFile logging to lwp_3ecbccb9_1983.log
# Time now: {1053543619} = Wed May 21 15:00:19 2003
# Time now: {1053543629} = Wed May 21 15:00:29 2003
LWP::UserAgent::new: ()
LWP::UserAgent::request: ()
LWP::UserAgent::send_request: GET http://192.168.1.1/Status.htm
LWP::UserAgent::_need_proxy: Not proxied
# Time now: {1053543633} = Wed May 21 15:00:33 2003
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 340 bytes
LWP::UserAgent::request: Simple response: Unauthorized
# Time now: {1053543634} = Wed May 21 15:00:34 2003
LWP::UserAgent::request: ()
LWP::UserAgent::send_request: GET http://192.168.1.1/Status.htm
LWP::UserAgent::_need_proxy: Not proxied
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 903 bytes
LWP::Protocol::collect: read 3770 bytes
LWP::UserAgent::request: Simple response: Internal Server Error
[download]

What can I do to prevent final (redundant) request from destoying $response->content?

Why doesn't $response->content retain accumulated response received?

Did you find a solution to this

Steve
steven.potter@sympatico.ca