When you use HTTP::Request::Common's
POST
routine, it creates an HTTP::Request
object that has all it's attributes set to the most
common values. For a large majority of tasks you will
not need to set the values to anything different, and
if you do, it is a great point at which to start from.
Now, HTTP::Message is the parent to HTTP::Request,
and passes down it's headers
method to it (along with all it's other methods) which will let you get at this request's
HTTP::Headers object.
Here is your example, modified to show the use of
this method:
#!/usr/bin/perl -w
use strict;
use HTTP::Request::Common qw(POST);
#build a pre-fab HTTP::Request object
my $request = POST 'http://gino/ciccio.cgi', [
sessionid => 'something',
mittente => 'something',
prefix => 'number',
numtel => 'number',
messagetext => 'message',
flash => 0,
Submit => ' Invia ',
];
#get this request's HTTP::Headers object
my $headers = $request->headers;
#you can call any method specified in HTTP::Headers' perldoc
print $headers->as_string;
-
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.