Any thoughts on what may be causing the headers to be included in the content?

I think broken webserver

For example

use CGI();
my $q = CGI->new;
print $q->header, $q->header, $q->Dump;
__END__

[download]
This will show headers in the content ... but its just content in the content .. everything after header is content

I'm not ruling out some odd /old misbehaving combination of LWP modules ... make sure you have the latest LWP...

then fix your arudino server

For diagnostics you might try using the following program and showing us the output 

use Data::Dump qw/ dd /;
use WWW::Mechanize;
my $ua = WWW::Mechanize->new;
$ua->get( $server_endpoint );
dd( $ua );
__END__

[download]

In reply to Re: LWP UserAgent response header in decoded_content by Anonymous Monk
in thread LWP UserAgent response header in decoded_content by jeff_e

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.