There are a few caveats that may not be obvious to everyone so I am going to cover them here but keep this in mind before starting. Before starting install epel or you will be missing tesseract: yum -y install epel-release #1) When you specify your SSL certificate with a full path, it really needs to exist where you tell it to (including the default location of /etc/ssl/certs and /etc/ssl/c........

cat .htaccess RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . index.php [L] I keep reading there is a "# BEGIN WordPress" and a "# END WordPress" in the wordpress htaccess above but there is clearly not. Even more strange is that my permissions are just 444 (read only). so i changed it........

It is really simple using .htaccess with mod_rewrite. Here is all you need: RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://site.com/$1 [R=301,L] Another more graceful way is to use the %{SERVER_NAME}variable to make it dynamic. Just be careful that the server name will always match what you expect. (eg. if you are doing load balancing or clustering what if the server name may be somethi........

The only real way us to do the following in the root of your site's .htaccess RewriteRule ^somedirectory-not-to-inherit/.*$ - [L]........

The below forces all request to your domain to go to the main non-www root domain. Updated code: RewriteCond %{HTTP_HOST} !=domain.com RewriteRule ^(.*)$ https://newurl.com/subdir/$1 [R=301,L] If you don't want it to go to a subdirectory: RewriteCond %{HTTP_HOST} !=domain.com RewriteRule ^(.*)$ https://newurl.com/$1 [R=301,L] Bad code: This code is bad beca........

The best way is as below in .htaccess using modrewrite, any request that is not SSL will be redirected to https://domain.com and the exact same URL RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://domain.com/$1 [R=301,L]........

This example is based on Wordpress but applies to any other query string eg. http://wordpress.com/?p=55 If you want to manually redirect that p=55 to /some/other/url how do you do it? RewriteCond %{QUERY_STRING} p=55 [NC] RewriteRule .* /new-url/? [R=301,L] You can change the p=55 to whatever your query string looks like. Remember to keep the "?" at the end of the new URLunless you really want the query s........

I struggled with this for awhile because sometimes you have rewritten URLs that you want to pass a query string but most of the info and examples do not support this. Take a typical example like this: RewriteRule ^(.*)-(.*)-(.*) /?module=$3&id=$2 You need to add the QSA flag to make it work like below: RewriteRule ^(.*)-(.*)-(.*) /?module=$3&id=$2 [QSA] The QSA preserves the original query string but also appends it wit........

I was getting frustrated with trying to write a simple URL like this: /example-withdash I used the htaccess code like this: Rewriterule ^example-withdash$ / [R=301] I also tried escaping the dash which I thought should have treated it as a literal but that didn't work either: Rewriterule ^example-withdash$ / [R=301] But it wouldn't work, apparently the "-" dash means don't substitute,........

This is something that happens a lot and it is very dirty, as you probably know each site is hosted on a certain IP address. Sometimes a domain is hosted by a single IP address and the IP address defaults to this very same domain. This means that if someone buys domain abcd.com and enters your IP address (the one of your website) as the A record, your content will show up on their domain as if it was their own. There is an easy way to prevent this by using .htacces........