The The There are two reasons to avoid the use of First<\/strong>: Performance – When AllowOverride<\/strong> is set to allow the use of To have a full view of the directives that it must apply, So, four file-system accesses were performed for each file access from a sub-directory content even if the file is not present.<\/p>\n\n\n\n Second<\/strong>: Security – granting users permission to make changes in To enable the Open the You should add the following configuration directive in the server’s virtual host file to allow the In the case of shared hosting, this is already allowed by the hosting service providers. All you need to do is to create a If your goal is to simply redirect one URL to another, the Redirect<\/strong> directive is the best option you can use. Whenever a request comes from a client on an old URL, it forwards it to a new URL at a new location.<\/p>\n\n\n\n If you want to do a complete redirect to a different domain, you can set the following:<\/p>\n\n\n\n If you just want to redirect an old URL to a new URL on the same host:<\/p>\n\n\n\n For a better user experience, load a custom error page when any of the links on your website point to the wrong location or the document has been deleted.<\/p>\n\n\n\n To create a custom 404 page, simply create a web page that will work as a 404 page and then add the following code to your You should change If you want to force your website to use HTTPS, you need to use the RewriteEngine<\/strong> module in the The following code snippet rewrites all the requests to HTTPS:<\/p>\n\n\n\n Let’s go through each line.<\/p>\n\n\n\n RewriteEngine on<\/strong> turns on the RewriteEngine<\/strong> module. This is required; otherwise, conditions and rules won’t work.<\/p>\n\n\n\n The first condition checks if Next, it checks if the HTTPS protocol was already entered by the user. %{https} off<\/strong> means that HTTPS protocol was not used.<\/p>\n\n\n\n When the RewriteCond<\/strong> is satisfied, we use RewriteRule<\/strong> to redirect the URL to HTTPS. Note that in this case, all URLs will be redirected to HTTPS whenever any request is made.<\/p>\n\n\n\n [ A free guide from Red Hat: 5 steps to automate your business<\/a>. ] <\/strong><\/em><\/p>\n\n\n\n Website owners often use the Common uses of .htaccess file The .htaccess file has several use cases. The most common examples include: When not to use .htaccess? The .htaccess file is commonly used when you don’t have access to the main server configuration file httpd.conf or virtual host configuration, which only … Continue reading .htaccess<\/code> file has several use cases. The most common examples include:<\/p>\n\n\n\n\n
When not to use .htaccess?<\/h2>\n\n\n\n
.htaccess<\/code> file is commonly used when you don’t have access to the main server configuration file httpd.conf<\/code> or virtual host configuration, which only happens if you have purchased shared hosting. You can achieve all of the above-mentioned use cases by editing the main server configuration file(s) (e.g., httpd.conf<\/code>) or virtual host configuration files, so you should not use .htaccess<\/code> when you have access to those files. Any configuration that you need to put in a .htaccess<\/code> file can just as effectively be added in a <Directory><\/strong> section in your main server or virtual host configuration files.<\/p>\n\n\n\nReasons to avoid using .htaccess<\/h2>\n\n\n\n
.htaccess<\/code> files. Let’s take a closer look at them.<\/p>\n\n\n\n.htaccess<\/code> files, httpd<\/code> will look for .htaccess<\/code> files in every directory starting from the parent directory. This will cause a performance impact, whether you’re using it or not. The .htaccess<\/code> file is loaded every time a document is requested from a directory.<\/p>\n\n\n\nhttpd<\/code> will always look for .htaccess<\/code> files starting with the parent directory until it reaches the target sub-directory. If a file is requested from directory \/public_html\/test_web\/content<\/code>, httpd<\/code> must look for the following files:<\/p>\n\n\n\n\n
\/.htaccess<\/code><\/li>\n\n\n\n\/public_html\/.htaccess<\/code><\/li>\n\n\n\n\/public_html\/test_web\/.htaccess<\/code><\/li>\n\n\n\n\/public_html\/test_web\/content\/.htaccess<\/code><\/li>\n<\/ul>\n\n\n\n.htaccess<\/code> files gives them full control over the server configuration of that particular website or virtual host. Any directive in the .htaccess<\/code> file has the same effect as any placed in the httpd<\/code> configuration file itself, and changes made to this file are live instantly without a need to restart the server. This can become risky in terms of the security of a webserver and a website.<\/p>\n\n\n\nEnable the .htaccess file<\/h2>\n\n\n\n
.htaccess<\/code> file, you need to have sudo\/root privileges on the server.<\/p>\n\n\n\nhttpd<\/code> configuration file of your website:<\/p>\n\n\n\n\/etc\/httpd\/conf\/test.conf<\/code><\/p>\n\n\n\n.htaccess <\/code>file in the DocumentRoot<\/strong> directory. If the following lines are not added, the .htaccess<\/code> file will not work:<\/p>\n\n\n\n<\/VirtualHost>\n<Directory \/var\/www\/test.com\/public_html>\n Options<\/strong> Indexes FollowSymLinks\n AllowOverride<\/strong> All\n Require<\/strong> all granted\n<\/Directory><\/code><\/pre>\n\n\n\n.htaccess<\/code> file in the public_html<\/code> directory to which the service provider has given you access and to which you will upload your website files.<\/p>\n\n\n\nRedirect URLs<\/h2>\n\n\n\n
# Redirect to a different domain<\/em>\nRedirect 301 \"\/service\" \"https:\/\/newdomain.com\/service\"<\/code><\/pre>\n\n\n\n# Redirect to a URL on the same domain or host<\/em>\nRedirect 301 \"\/old_url.html\" \"\/new_url.html\"\nLoad a custom 404 Error page<\/code><\/pre>\n\n\n\n.htaccess<\/code> file:<\/p>\n\n\n\nErrorDocument<\/strong> 404 \/error\/pagenotfound.html<\/code><\/pre>\n\n\n\n\/error\/pagenotfound.html<\/code> to the location of your 404 page.<\/p>\n\n\n\nForce the use of HTTPS instead of HTTP for your website<\/h2>\n\n\n\n
.htaccess<\/code> file. First of all, you need to turn on the RewriteEngine<\/strong> module in the .htaccess<\/code> file and then specify the conditions you want to check. If those conditions are satisfied, then you apply rules to those conditions.<\/p>\n\n\n\n# Turn on the rewrite engine<\/em>\nRewriteEngine<\/strong> On\n\n# Force HTTPS and WWW<\/em>\nRewriteCond<\/strong> %{HTTP_HOST} !^www\\.(.*)$ [OR,NC]\nRewriteCond<\/strong> %{https} off \nRewriteRule<\/strong> ^(.*)$ https:\/\/www.test-website.com\/$1 [R=301,L]<\/code><\/pre>\n\n\n\nwww<\/code> is entered. [OR, NC]<\/strong> stands for no case<\/em>, which means even if the entered URL has a mix of upper or lowercase case letters.<\/p>\n\n\n\nWrap up<\/h2>\n\n\n\n
.htaccess<\/code> file to control the behavior of their website. In this article, we have covered the basics of the .htaccess<\/code> file and some common use cases in place on most of the websites.<\/p>\n","protected":false},"excerpt":{"rendered":"