#APACHE TOMCAT ERROR 403 CODE#

Is also forbidden due to its similar ability to circumvent directory restrictions So now if you check the Apache's log message( tail -n 50 -f /var/www/html/) you'll see such an error: Options FollowSymLinks and SymLinksIfOwnerMatch are both off, so the RewriteRule directive This was the case for me and made me pull my hair until I found out the cause! Notice that another issue that might be causing this is that, the 'FollowSymLinks' option of a parent directory might have been mistakenly overwritten by the options of your project's directory. conf files, try running the find command, such as: $ find / -name nf PS: If you are having trouble finding these. The command for this will depend on your OS and installation, so google that separately if you need help with it.

Once you have saved your changes, restart Apache. This change has been a major source of confusion for googlers of this problem, such as I, because copy-pasting these Apache 2.2 lines will not work in Apache 2.4+, and the Apache 2.2 lines are still commonly found on older help threads. Note that if you are using Apache 2.2, these lines should instead say Order allow,deny Without these, you will not be overriding the default Apache settings specified in nf. Options Indexes FollowSymLinks Includes ExecCGIĪre critical for Apache 2.4+. # ServerAdmin '/Users/myusername/Sites/mySite/public'

For me, that's within the public subdirectory. The DocumentRoot and Directory paths should be identical, and should point to wherever your index.html or index.php file is located. Add an entry for your webpage if you don't already have one. Now, open the nf file that you just Included. (Your exact path may be different.) # Virtual hosts Notice that in your nf file, you will see a default configuration like this (Apache 2.4+): ĭO NOT change this! We will not override these permissions globally, but instead in your nf file.įirst, however, make sure that your vhost Include line in nf is uncommented. Then your problem is not with your file permissions, but instead with your Apache configuration. If your error_log says something like: client denied by server configuration: However, I encountered a different error (the one below) which I fixed as follows: If you still get the error that says search permissions are missing on a component of the path, I don't know what you should do. You can do this from the terminal by: $ cd. Then, refresh the URL where your website should be (such as If you're still getting a 403 error, and if your Apache error_log still says the same thing, then progressively move up your directory tree, adjusting the directory permissions as you go.

You can fix them by running these commands from the terminal: $ cd /Users/myusername/Sites/mySite Then there is a problem with your file permissions. '/Users/myusername/Sites/mySite') because search permissions If it says something like: access to /mySite denied (filesystem path Here's what worked for me:įirst, check your Apache error_log file and look at the most recent error message. Match of 'within ' against 'REQUEST_METHOD' required.I just fixed this issue after struggling for a few days.

#APACHE TOMCAT ERROR 403 CODE#

Here's the error log: ModSecurity: Access denied with code 403 (phase 1). My Apache server has the mod_security in it configured with OWasp rules. I linked Apache with Apache Tomcat and last night, it was working fine until when I tried running the system again today, it gave me an access denied error.

Apache tomcat error 403