Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 59149 invoked from network); 18 Jun 2009 14:23:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Jun 2009 14:23:25 -0000 Received: (qmail 7212 invoked by uid 500); 18 Jun 2009 14:23:35 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 7189 invoked by uid 500); 18 Jun 2009 14:23:35 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 7181 invoked by uid 99); 18 Jun 2009 14:23:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2009 14:23:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of acaloiar@gmail.com designates 209.85.217.207 as permitted sender) Received: from [209.85.217.207] (HELO mail-gx0-f207.google.com) (209.85.217.207) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2009 14:23:27 +0000 Received: by gxk3 with SMTP id 3so4126922gxk.10 for ; Thu, 18 Jun 2009 07:23:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=7HUcxdt++RWQyNQj6VHcB/FwbyU0Erwsmb8acWd/HRQ=; b=iTJ6sCBPE06fFDnQwPlEjMjn/B6Y9HC3r44si00b9KooncIJyT/EzIQtPhqmgrYw8t Tz+loi2dWjdmCnPds5mttqzS6tuLOn2oiq+Xh9TCBEDP2r9ZLBEiRzeU5uACbN6/69jO JR+s0Ov8RgG9XRnhlxooeOMiFT1zQsQc84UJ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=gcsu89e3W/+sfzP0iKCbmQ2AueNlp77xqVNERHuvCL8lErW4Bclf8bUIiiBpXEW0tD pNEcpJWkrdt5Zzt0EhfsYiibvHwtvsOBL6rhBfYb0ftvP1O2vVBjjF6345Y3eMRwWU0V yznqXrlyzrzs17YcfzVXcKAZ3yWh28Ux2uK6g= MIME-Version: 1.0 Received: by 10.90.83.2 with SMTP id g2mr1153310agb.116.1245334986137; Thu, 18 Jun 2009 07:23:06 -0700 (PDT) From: Adriano Caloiaro Date: Thu, 18 Jun 2009 10:22:46 -0400 Message-ID: Subject: mp2 / Apache byterange filter To: modperl@perl.apache.org Content-Type: multipart/alternative; boundary=001636283644799f4b046ca02579 X-Virus-Checked: Checked by ClamAV on apache.org --001636283644799f4b046ca02579 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, Could someone point me in the correct direction to support byte range responses in mod_perl2? From what I've read, Apache should understand that it needs to apply the byterange filter whenever $r->sendfile is used on a large file and the Range: header is present in the incoming request. However what I'm seeing is that the entire file is returned for each byte range requested by the client. Access log serving off disk in Apache2: *.*.*.* - - [17/Jun/2009:19:50:30 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 206 1 "-" "-" *.*.*.* - - [17/Jun/2009:19:50:31 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 206 435996 "-" "-" *.*.*.* - - [17/Jun/2009:19:50:30 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 206 2097152 "-" "-" Serving from perl handler: *.*.*.* - - [18/Jun/2009:10:11:43 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 200 2533148 "-" "-" *.*.*.* - - [18/Jun/2009:10:11:45 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 200 2533148 "-" "-" *.*.*.* - - [18/Jun/2009:10:11:45 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 200 2533148 "-" "-" It would seem like re-invited in the wheel if I were to implement RFC 2616 in perl when there is a byterange filter already present in apache. Thank you for any help! -Adrian --001636283644799f4b046ca02579 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

Could someone point me in the correct direction to support by= te range responses in mod_perl2?=A0 From what I've read, Apache should = understand that it needs to apply the byterange filter whenever $r->send= file is used on a large file and the Range: header is present in the incomi= ng request.=A0 However what I'm seeing is that the entire file is retur= ned for each byte range requested by the client.=A0

Access log serving off disk in Apache2:

*.*.*.* - - [17/Jun/2009= :19:50:30 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 20= 6 1 "-" "-"
*.*.*.* - - [17/Jun/2009:19:50:31 -0400]= "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 206 435996 "-= " "-"
*.*.*.* - - [17/Jun/2009:19:50:30 -0400] "GET /mygcx/test/flvplayernew= 17.flv HTTP/1.1" 206 2097152 "-" "-"

Servin= g from perl handler:

*.*.*.* - - [18/Jun/2009:10:11:43 -0400] "= GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 200 2533148 "-"= "-"
*.*.*.* - - [18/Jun/2009:10:11:45 -0400] "GET /mygcx/test/flvplayernew= 17.flv HTTP/1.1" 200 2533148 "-" "-"
*.*.*.* - = - [18/Jun/2009:10:11:45 -0400] "GET /mygcx/test/flvplayernew17.flv HTT= P/1.1" 200 2533148 "-" "-"


It would seem like re-invited in the wheel if I were to implement R= FC 2616 in perl when there is a byterange filter already present in apache.= =A0 Thank you for any help!

-Adrian



--001636283644799f4b046ca02579--