Project

General

Profile

Actions

Feature #57

closed

more flexible bandwidth limiting (like Apache mod_bandwidth/mod_throttle)

Added by Anonymous over 16 years ago. Updated about 13 years ago.

Status:
Wontfix
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

I would like to limit my outgoing bandwidth by specifying policies on different levels:
  • per-directory
  • per-virtualserver
  • per-user

In example:

users who match pattern http://username.example.org would have 10kb/s output max, and users using http://example.com would have 20kb/s at max.

It's basicly the same as in Apache's mod_bandwidth.

-- Louis

Actions #1

Updated by conny over 15 years ago

The question is how different people define "_user_": does that refer to a virtual site, a local userid, a remote authenticated user, or the remote IP address?

Actions #2

Updated by conny over 15 years ago

Note: Related but not entirely the same is the principle of simple per-remote-IP concurrency limits, like those made available for Lighttpd by source:browser/branches/lighttpd-merge-1.4.x/src/mod_evasive.c#896.

Actions #3

Updated by stbuehler about 13 years ago

  • Status changed from New to Fixed
  • Resolution set to wontfix

connection.kbytes-per-second should basically do what you want for directory and vhost, evasive.max-conns-per-ip for user.

Actions #4

Updated by stbuehler about 13 years ago

  • Status changed from Fixed to Wontfix
Actions

Also available in: Atom