New answers tagged

3

RewriteCond %{REQUEST_URI} !^/Joomla3 RewriteRule ^(.*)$ Joomla3/$1 [L] What these directives do is... if the requested URL does not start "/Joomla3" then internally rewrite the request to the "Joomla3" folder. What you need to do is add another condition to state that... if the requested URL does not start "/Joomla3" and it does not start "/owncloud" ...


1

DirectoryIndex test.html is not ordinarily done in .htaccess. In order for it to work in .htaccess, you will need AllowOverride All (or something similar) within your sites .conf file. Ordinarily, DirectoryIndex test.html is placed in the sites .conf file. This is the best place for this directive. Where you find your .conf files all depends upon your ...


1

The only way to be sure why you are receiving a 403 error is to check the logs. They will tell you the reason why it is forbidden. The DirectoryIndex itself doesn't create any new rule that would provide a 403 error. However, if the error began after you made that change, you likely have Options -Indexes, or a similar line, which gives a 403 message rather ...


2

A site doesn't have to have a .htaccess file. If you don't have a .htaccess file, your site will run on the settings in the apache and PHP server configuration files. Having your file named .htacces.txt (or .htaccess.bak for that matter) will not have any effect on your server, it won't refer to the file for any settings. If you then rename your file to ...


2

Firstly if the file is named htaccess.txt then that means the htaccess file is not enabled as only the file named .htaccess will work. Secondly if you are getting a 500 error when you enable the .htaccess file you either have an error in your htaccess syntax or overrides are not supported. You would need to check the error logs to see which one it is. Some ...



Top 50 recent answers are included