[mirror-admin] enabling keep-alives

[Günther Fischer]

With this rewrite rule I see also som problem - the range mechanism is
a good thing for very log files.
If I couldn't support that, I think it is better to redirect to ftp,
where I have the reget/partial transfers.

I have set the MaxConnPerIP to 20 now and will see.

Yes I see now in acess.log the partial gets  code 203 and some 503 for
over MaxConnPerIP.
If you grep for some sample IPs you can see this clearly.

On Wed, Mar 26, 2008 at 4:52 PM, Stuart McKim <mckim at osuosl.org> wrote:
> On Tue, Mar 25, 2008 at 10:22:15PM +0200, Axel Thimm wrote:
>  > The other is to block ranged requests as this is what download
>  > accelerators do indeed:
>  >
>  >     RewriteEngine on
>  >     RewriteCond %{HTTP:Range} [0-9]$
>  >     RewriteRule \.iso$ / [F,L,R=403]
>  >
>
>  Does this also block all legitimate download resumes by clients? For
>  example, if I lose my connection while downloading something from home,
>  I'll use a 'wget -c URL' to pick up where I left off. From my
>  understanding of this rule, it would block that.
>
>  More to the point, is there a way to see if multiple range requests are
>  active for the same file from the same IP? That seems to be what we
>  really want to accomplish.
>
>  Stuart
>
>  --
>  Stuart McKim
>  FTP Administrator
>  Open Source Lab
>  Oregon State University
>
> --
>



-- 
Mit freundlichen Grüßen / Regards
Günther Fischer

--