I started seeing weird behavior from LWP (5.835) when accessing the Bing API. In particular, I'm doing something like this: $response = $ua->request(GET $url);

The problem is $response->content intermittently (~50% of the time) returns only a partial JSON response.

When that happens, the header reads like this: 

HTTP/1.1 200 OK
Connection: close
Date: Sun, 24 Oct 2010 15:24:50 GMT
Content-Length: 38511
Content-Type: application/json; charset=utf-8
Client-Aborted: die
Client-Date: Sun, 24 Oct 2010 15:24:50 GMT
Client-Peer: 72.246.30.144:80
Client-Response-Num: 1
X-Died: read failed: Connection reset by peer at /usr/local/lib/perl5/
+site_perl/5.8.9/LWP/Protocol/http.pm line 388.

[download]

I see the error in the X-Died header as the docs suggest. However, if I use curl/wget/lynx/whatever on the same machine I get the full response every time.

Any ideas?

In reply to Partial content from LWP by yegg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.