mod_ratelimit is broken in the current release and due to be fixed in the next update. On Wed, Aug 29, 2018 at 4:07 PM Aram Akhavan <aram.akhavan@xxxxxxx> wrote: > > I'm trying to use mod_ratelimit to enable bandwidth limiting on my entire apache server. > > If I add the following to my apache2.conf: > > SetOutputFilter RATE_LIMIT > SetEnv rate-limit 1024 > SetEnv rate-initial-burst 1024 > > my indexes stop working. The same thing happens if I add it within a <Location "/">. I'm using fancy-index, and have copied the contents of its .htaccess into my mods-enabled/autoindex.conf > > The html that the server returns when I access an index is > > <!DOCTYPE html> > <html> > <head> > <meta charset="utf-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1.0"> > <title></title> > <link rel="stylesheet" type="text/css" href="/fancy-index/style.css"> > </head> > <body> > > If I instead add those rate limit lines to a <Directory> directive, then the indexing is fixed, and rate limiting works on that folder. However, I'm trying to use this to rate-limit Nextcloud downloads, and applying the limit to that virtual host or the root directory doesn't seem to work at all, hence my desire to apply the rate-limiting to the entire server. > > Thanks, > > Aram -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|