Hot answers tagged

2

No, you can only use one distributed config file per directory. You should avoid using .htaccess files completely if you have access to httpd main server config file use a <Directory> block instead.


2

A Deny block still requires apache to process the request far enough to see that it matches a deny, and is most likely equal in 'cost' as a 404. You say 'DOS' but do you mean an actual attack or is it random scanners? Random scanners don't normally drive enough traffic to make 404's/403's for those a problem. Is this behind an ELB? If not you should be ...


2

For this to be possible, you would need a valid SSL certificate for 111.111.11.111, which is unlikely, see also Is it possible to have SSL certificate for IP address, not domain name?. What you probably want to do is: Create a VirtualHost entry matching 111.111.11.111 as ServerName, but not using https, but http instead. Redirect that to your domain. ...


1

Adding the below apache rewrite rules should do the trick for you. RewriteEngine On RewriteBase / # first redirect RewriteCond %{HTTP_HOST} !domain.com$ [NC] RewriteRule ^(.*)$ https://newdomain.com/$1 [L,R=301] # second redirect RewriteCond %{HTTP_HOST} !example1.com$ [NC] RewriteRule ^(.*)$ https://example2.com/$1 [L,R=301] The above rules will do a ...


1

Neither one is specifically configured to handle ssl requests. In this case neither one should be listen at the port 443 at all, i.e. the browser should not be even able to connect to this port. Since you get responses or error messages the browser is obviously able to connect to this port so something is obviously setup to deal with this port. But it ...



Only top voted, non community-wiki answers of a minimum length are eligible