So does this mean that the content-length header value is no longer used?
Here is some untested sample code based on your response and reading the lwp::useragent docs...
use strict;
use warnings;
use LWP;
use IO::Handle;
use Fatal qw( open close );
my $url = 'https://........';
my filename = 'file2send.txt';
my $LINES_PER_CHUNK = 100;
open my $fh, '<', $filename;
sub sendthis {
my @buf;
my $linesread = 0;
if ($fh->isopened) {
while (my $line = <$fh>) {
$linesread++;
push(@buf, $line);
if ($linesread == $LINES_PER_CHUNK) {
return join('', @buf);
}
}
close $fh;
return join('', @buf);
}
return '';
}
eval {
my $headers = HTTP::Headers->new();
$headers->header('Content-Type' => 'text/plain; charset=utf-8');
$headers->header('Content-Length' => -s $file2send);
my $request = HTTP::Request->new('POST', $url, $headers);
$request->protocol('HTTP/1.1');
my $browser = LWP::UserAgent->new();
my $response = $browser->request($request, \&sendthis);
my $gotthis = $response->content();
print $gotthis;
};
if ($@) {
# handle error !
}
Edit: made changes that rhesa suggested regarding request method callback and content length
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|