Limit Download Speed with Apache

By  on  

My adventures into retro gaming have brought me back into the semi-seedy world of piracy websites and the technology considerations that dictate their business model.  Annoying popups and pornographic advertisements aside, the most obvious technological observation I made was that each of these sites used bandwidth throttling as a way to make money.  Want that game to download quickly?  Stump up $10 per month and it will be lightning fast; otherwise you're relegated to sleep-inducing download speeds.

In researching download speed limits, it became apparent that dynamic rate limitation is incredibly inefficient, and that the best way to throttle downloads is by configuring different servers or virtual directories with different download speeds, and directing each user to each server based on the download speed they should have.

Configuring Apache's Download Speed Limit

To throttle the download speed on Apache servers, enable the mod_ratelimit extension:

<!-- Requires 2.4+ -->
LoadModule ratelimit_module modules/mod_ratelimit.so

Then set different download speeds by directory with the following Apache configuration:

<IfModule mod_ratelimit.c>
    <!-- 100kb/second limit -->
    <Location /tier1>
        SetOutputFilter RATE_LIMIT
        SetEnv rate-limit 100
    </Location>

    <!-- 500kb/second limit -->
    <Location /tier2>
        SetOutputFilter RATE_LIMIT
        SetEnv rate-limit 500
    </Location>
</IfModule>

Some type of dynamic Apache config would allow custom URLs per user which would obscure download speed URLs so users couldn't dynamically spoof URLs to get some else's download speed.

The download speed limit and throttling business seems booming: just look at MEGA and other likewise services.  The science behind download throttling is big business and I hope to learn more about it.  In the mean time, it's nice to know that download speed limitation can be done with a few Apache directives!

Recent Features

  • By
    JavaScript Promise API

    While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready?  Promises are becoming a big part of the JavaScript world...

  • By
    How to Create a RetroPie on Raspberry Pi &#8211; Graphical Guide

    Today we get to play amazing games on our super powered game consoles, PCs, VR headsets, and even mobile devices.  While I enjoy playing new games these days, I do long for the retro gaming systems I had when I was a kid: the original Nintendo...

Incredible Demos

  • By
    DWRequest: MooTools 1.2 AJAX Listener &#038; Message Display

    Though MooTools 1.2 is in its second beta stage, its basic syntax and theory changes have been hashed out. The JavaScript library continues to improve and become more flexible. Fellow DZone Zone Leader Boyan Kostadinov wrote a very useful article detailing how you can add a...

  • By
    Submit Button Enabling

    "Enabling" you ask? Yes. We all know how to disable the submit upon form submission and the reasons for doing so, but what about re-enabling the submit button after an allotted amount of time. After all, what if the user presses the "stop"...

Discussion

  1. is it possible to limit only download thread for download managers?? like In internet download manager there is setting up to 32 threads.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!