Hot answers tagged apache-2.2
Your certificate was issued to CN=*.example.com and does not contain X509v3 Subject Alternative Name for the following domains: *.example.com example.com You need to get a new certificate. Check out https://en.wikipedia.org/wiki/Subject_Alternative_Name You can dump your certificates with the following command, to verify: openssl x509 -text -in &...
Your use-case is the text-book example of when to completely avoid rewrite rules. To redirect http URLs to https, simply do the following: <VirtualHost *:80> ServerName www.example.com Redirect "/" "https://www.example.com/" </VirtualHost> <VirtualHost *:443> ServerName www.example.com # ... SSL configuration goes here ...
You should add this line just after the two RewriteCond and before your RewriteRule: RewriteRule ^/$ http://www.mynewdomain.com/pageA [L,R=301] If this rule doesn't match then the original will be evaluated. It is important that this rule be before your original rule. Regards Paolo B.
On your instance, run host ec2-123-123-123-123.eu-central-1.compute.amazonaws.com (your instance's public DNS hostname). See that it does not, in fact, resolve to 126.96.36.199, but rather to an RFC 1918 address (probably 10.x.x.x)? Amazon uses split-view DNS, so the hostname resolves to the public IP outside the region/VPC, but resolves to the private ...
Only top voted, non community-wiki answers of a minimum length are eligible