Differences

This shows you the differences between two versions of the page.

--- apache_htaccess_centos [2015/03/30 07:41] – created luke7858
+++ apache_htaccess_centos [2024/05/23 07:26] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ==== htaccess for apache ====
+\\
+.htaccess allows for management of webserver configuration and can be used for things link: specifying protecting of a location, protecting wp-admin login for wordpress and configuring mod_rewrites. To use the .htaccess file you will need to allow the file the ability to override all. This will need to be configured in the apache config file or the vhost itself. \\
+If you change the apache configuration file then this will allow it for all vhosts created. If you allow the .htaccess in a vhost config file then it will only work for that specific vhost.
-.htaccess to can be used to specify protecting of a location or protect wp-admin login for wordpress. To use the .htaccess file you will need to allow the file the ability to override all. This will need to be configured in the apache config file AND the vhost itself. You may have to uncomment the section in the **/etc/httpd/conf/httpd.conf** file. The section looks similar to:
+You may have to uncomment the section in the **/etc/httpd/conf/httpd.conf** file. The section looks similar to:
 <sxh bash>
@@ Line 21: / Line 24: @@
 Order allow,deny
 allow from all
-# Uncomment this directive is you want to see apache2's
-# default start page (in /apache2-default) when you go to /
-#RedirectMatch ^/$ /apache2-default/
 </Directory>
 </sxh>
+\\
+=== Basic http File Protection (authentication) ===
 This example shows the file being used to protect the specific file that admins use to log into the wordpress site (wp-login.php), you can change this to what ever file you wish to protect. Add this section to the file:
@@ Line 37: / Line 38: @@
 </Files>
 </sxh>
+\\
+=== Document Path Protection (authentication) ===
+<sxh bash>
+<Directory "/www/docs/private">
+    AuthName "Private"
+    AuthType Basic
+    AuthUserFile /var/www/html/.htpasswd
+    Require valid-user
+</Directory>
+</sxh>
 \\
 === Mod_rewrite apache ===
@@ Line 64: / Line 74: @@
 You can use an online generator to produce the .htpasswd username and hashed password or you can do it via the command line.
+== Command Line Example ==
+Change the path below to where you wish to store the password file
+<sxh bash>
+htpasswd -c /var/www/.htpass username
+</sxh>
 **Example:**
@@ Line 73: / Line 87: @@
 webdeveloper:dhaNI0w8ajGTUskliasun(U*&HKks/
 </sxh>
+ \\
+=== phpMyAdmin .htaccess ===
-htaccess for nginx (http auth)
-nginx does not support .htaccess, more information can be found at the following link on why it doesn’t: http://www.nginxtips.com/why-doesnt-nginx-support-htaccess-files/
-If you are lazy and you already have a .htaccess file then you can use the following link to convert that into nginx format: htaccess to nginx
-The standard format for the htaccess would be:
-location ^~ /secret_directory/ {
-auth_basic "Restricted";
-auth_basic_user_file /var/www/html/.htpasswd;
-You add this code to the vhost (server block), change secret directory to the location or file you wish to protect, restart/reload nginx and you are done!
-Just incase you are still confused the following code is what I use for my website:
-# nginx configuration
-location /wp-login.php {
-auth_basic_user_file /var/www/html/.htpasswd;
-auth_basic "hello";
-}
-Please note: you will still need the .htpassword file and will need to specify the location.
-mod_rewrite for nginx
-For mod_rewrite you will need the following code:
-try_files $uri $uri/ /index.php?args;
-phpMyAdmin .htaccess
-CentOS
 To password protect phpMyAdmin you should edit /etc/httpd/conf.d/phpMyAdmin. In this file you should then add the following code:
+<sxh bash>
 AuthType Basic
 AuthName "Enter account information"
 AuthUserFile /var/www/html/.htpasswd
 Require valid-user
+</sxh>
 AuthUserFile – this should reference the .htaccess password file you have set up previously