Tag Info

New answers tagged

1

Not possible, sorry. As per my statement on The Apache Modules Guide: Thus, the server itself does not presume to know which module is responsible for handling a specific request, and will ask each module whether they have an interest in a given request or not. It is then up to each module to either gently decline serving a request, accept serving it or ...


0

Try to find and remove/comment AddType x-mapp-php5 .php AddHandler x-mapp-php5 .php from your apache configs and .htaccess file.


1

There is no issue with having a high number of spare httpd processes always running. It's actually a good idea. The main point is : if you want httpd to reach that number of process, you'd better reach if right from the start and be sure it works. In other words, don't auto-scale, simply pre-scale. Less surprise. The seconday point is : if you don't need ...


0

Every Directive lists the context in which it is valid. In other words where it is allowed to be used. The context can be any combination of: s - server config This means that the directive may be used in the server configuration files (e.g., httpd.conf), but not within any <VirtualHost> or <Directory> containers. It is not allowed in ...


1

I'm concerned about your testing methodology. It appears you're just spawning a whole bunch of processes then looking at their memory usage. The problem is that when they're first spawned, they're sharing a maximal amount of memory, and don't have any local, per-process data stored. When you start actually using them, you'll find that those processes ...


1

What your trying to avoid is incoming requests causing new processes to be forked at a rate higher than older processes can service the older connections. This risk is causing a situation where the system keeps creating new processes that consume the available memory and starts to increase the frequency in which the operating system uses swap. Which in turn ...


0

Try just "66.249" because it's not a regex.


0

if you want server-wide, then you can use this in your httpd.conf: <Directory /var/www/vhosts/*/httpdocs> SetEnvIf Referer spammer-one\.com spammers SetEnvIf Referer spammer-two\.com spammers SetEnvIf Referer spammer-three\.com spammers Order Allow,Deny Allow from all Deny from env=spammers </Directory> Replace /var/www/vhosts/*/httpdocs ...


1

The simpleSAMLphp installation procedure is documented on the simpleSAMLphp website. It states there that only the www folder has to be available from the internet, which can be achieved by aliassing /simplesaml. It looks like you're doing that. Not knowing anything about your setup, I can not possibly know if you won't break anything by doing this. ...


0

Yes this sound like a pretty simple one to solve from what I understand. I would first address your haproxy configuration and make a tad more efficient by using ACL's to detect if the requested account is a critical or not critical :-) You will need to add this to your front end: acl critical_1 path_beg /~accname1 acl critical_2 path_beg /~accname2 ...



Top 50 recent answers are included