Getting 403 forbidden on all xml files on the server

apache-2.2xml

I recently moved a site to a new server where the server configuration is not allowing access to xml files:

[error] client denied by server configuration: /var/www/website/test.xml

After further testing, I get a 403 (forbidden) when trying to load any xml files.
How do I enable server xml files in apache? I'm assuming it's an apache configuration.

Thanks!

Solution:
my .htaccess had:

<Files ~ "\.(xml)$">
    deny from all
</Files>

I removed the above htaccess directive and denied only the xml files that shouldn't be accessed directly.

Best Answer

Your Apache Allow/Deny directives are configured to forbid access to the file you're trying to get.

These directives will likely be in your <VirtualHost> configuration, or an .htaccess file. Please edit your question with this info and we can assist in straightening out the rules.

Related Solutions

Centos – WebDAV on CentOS – getting 403 error when attempt to upload

I recently struggled with the same problem on my Fedora 10 system. In my case the culprit was some odd redirection that I was doing in Apache. Specifically, I use a content management system (Drupal, to be exact) that within it's .htaccess includes the following redirection logic to redirect missing files to a PHP script:

# Rewrite URLs of the form 'x' to the form 'index.php?q=x'.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

It makes sense that the above only affects the PUT method since in that case REQUEST_FILENAME does not exist.

Not having the WebDAV area inside of the Drupal area, which seems like a reasonable constraint, fixes the problem.

Also, I think it is likely that SELinux would result in a different error, but it's not mentioned in the discussion above. Did you try disabling SELinux?

Debian – Apache & Subversion, “403: Forbidden” remote but local still works

You should be using HTTPS for SVN. Don't want to be sending proprietary source code over plaintext.

The problem likely relates to a statement similar to this:

order allow,deny
deny from all

Which restricts access to most files on the web server at the top level of the httpd.conf.

You should add this to the Location node to override this:

order allow,deny
allow from all

Hope that helps... Best, -Henry

Best Answer

Related Solutions

Centos – WebDAV on CentOS – getting 403 error when attempt to upload

Debian – Apache & Subversion, “403: Forbidden” remote but local still works

Related Topic