Using the "Host:" header with HTTP/1.0 is acceptable. Web servers that supports virtual hosts almost always support it. Ancient web servers that don't support virtual hosts will usually just ignore the header. It is safest to always include the "Host" header with HTTP/1.0 requests.

More importantly, the HTTP/1.1 protocol has requirements for clients that manual scripts aren't willing to do. For example, HTTP/1.1 clients must support chunked encoding. And handle persistent connections gracefully. Clients don't want a persistent connection should send "Connection: close" header.

In reply to Re: Re: read aka fread(3) broken, sysread aka read(2) works IIS socket by iburrell
in thread read aka fread(3) broken, sysread aka read(2) works IIS socket by tachyon

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.