It turned out that setting status to 206 before call of $r->send_http_header solved the problem. Here is a fixed version of code:
my $range_request = ($mod_perl::VERSION < 1.99) ? $r->set_byte +range : 0; if((my $status = $r->meets_conditions) eq OK()) { if ($mod_perl::VERSION < 1.99) { if ($range_request) { $r->status(206); }; $r->send_http_header; }; } else { return $status; } return OK() if $r->header_only; if($range_request) { while(my($offset, $length) = $r->each_byterange) { $r->print(substr($contents, $offset, $length)) +; } } else { $r->print($contents); } return OK();

In reply to Re: mod_perl handler inside apache 1.x serving partial content - is this possible? How? by Anonymous Monk
in thread mod_perl handler inside apache 1.x serving partial content - is this possible? How? by Anonymous Monk

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.