Tag Info

New answers tagged

0

You can use mod_qos and its QS_SrvMaxConnPerIP to limit how many connections can be made by a given IP address. That can prevent it as long as the attacker isn't using too many different IP addresses. If you have MaxClients of 150 and QS_SrvMaxConnPerIP of 45, they could attack from 3 different IPs and you'd have 15 connections available (150 - (45*3) = ...


1

track_uploads syntax: track_uploads < zone_name> < timeout> default: n/a context: location This directive enables tracking uploads for the current location. Each POST landing in this location will register the request in the zone_name upload progress tracker. Since Nginx doesn't support yet RFC 1867 upload, the location must be ...


1

YES! Base on what Zoredache said I did a :/etc/apache2$ rgrep post * which found sites-available/000-default.conf: php_value post_max_size 128M so a little /etc/apache2/sites-available$ sudo vi 000-default.conf change php_value post_max_size 128M to 1024M and I am done!


2

To install additional modules you must compile nginx from source. Download and extract source of nginx (download links) Download and extract source code of desired module's (revision) Compile nginx with module Actual commands should look something like this: wget -P /tmp http://nginx.org/download/nginx-1.6.2.tar.gz tar -zxvf /tmp/nginx-1.6.2.tar.gz -C ...


0

When I want to change the file modification time, I use an FTP client on the console. Log on with ftp ftp.example.com, then cd commands go to the correct directory SITE command to move the extended command mode UTIME somefile.txt 20050101123000 20050101123000 20050101123000 UTC Change the access time, modification time, it's time to create a directory ...


2

I realize the original poster is no longer in need of a solution, but here's my take on the best solution for this issue. I also realize the poster would prefer to use Ubuntu, but configuring the routing rules manually like that isn't great for transferring ownership to others or even referencing yourself years later. I personally would suggest a more ...


0

If you're using NGINX or other proxy server, it may be related to it's client_max_body_size directive. To fix it create folder .ebextensions in app root, and a file .ebextensions/01_nginx.config. Then tell build script to add this directive while building your environment, adding this to your created .ebextensions/01_nginx.config: container_commands: ...



Top 50 recent answers are included