Your client is not an HTTP client. It completely ignores the Content-Length header which tells the length of the response body. That is the mechanism HTTP uses to indicate when the response ends. Instead, it reads the response by lines which fails as you discovered when the response does not end with a LF. The solution is to read the response header by line, parse out the Content-Length, and then read the body by blocks.
Also, your client should not advertise HTTP 1.1 if it does not support it. Real HTTP will assume they can use stuff like chunked encoding and your client won't handle it.
Finally, is there a reason you can't use LWP for the HTTP client? Or HTTP::Daemon for the server? Both of them handle all the nasty details of the HTTP protocol.
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.