There are no requirements about how HTTP requests are put in packets. HTTP works over TCP and only deals with connection streams. Dividing into packets is up to the TCP stack of the operating system.
Applications can influence when packets are sent by flushing buffers. LWP::UserAgent probably does two separate write for the header and the POST body, and the OS sends that as two packets.
Either you or the network sniffer aren't giving the real HTTP header. But it looks like a proper HTTP POST, with the Content-Type, Content-Length, and url encoded body.
Any application that wants to reliabily examine HTTP must be able to reassemble the stream from packets. Depending on clients to send the header and enough of the POST body in the same packets is unreliable.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.