[SOLVED] Strange permissions issue with files in Apache.

fatherjack · 04-05-2016, 04:16 PM

Hi All.

I'm having issues with directory listings in Apache on a CentOS 6 (x64) box.

The scenario:

I'm logged into the server as root, and am in the /var/www/html/mydir directory.

I've downloaded a file using wget from another server, but the file does not show in a directory listing when viewed from a browser.

The file permissions look to be good, and changing them to 777 does not help, however doing a cp filename newfilename against this file creates an identical copy that IS visible in a directory listing. The file permissions and ownership look identical, and I cannot see any difference between the two files. Am I missing something here?

Thanks.

bathory · 04-06-2016, 02:42 AM

Quote:

The file permissions look to be good, and changing them to 777 does not help, however doing a cp filename newfilename against this file creates an identical copy that IS visible in a directory listing. The file permissions and ownership look identical, and I cannot see any difference between the two files. Am I missing something here?

What happens if you try to GET the file directly, like: http://myhost/mydir/filename
BTW you should use 644 for the files in the webserver and 755 for directories

fatherjack · 04-06-2016, 08:12 AM

Hi Bathory

Thanks for the reply.

So if I try a direct on the files, I get a 403 Forbidden (as expected):

You don't have permission to access /mydir/myfile.zip on this server.

Furthermore, I tried a known non-existent file, and received a 404 as I'd expect.

Also, to your point about permissions, 644 is what I have for the files - I gave 777 as an example to show that even the most permissive mode resulted in failure. File permissions are as below:

-rw-r--r--. 1 root root 361482835 Mar 25 12:09 myfile-copy.zip
-rw-r--r--. 1 root root 361482835 Mar 25 12:37 myfile.zip

Also I did an md5sum, and the checksums came up identical.

Thanks.

bathory · 04-06-2016, 08:46 AM

Doh strange indeed,
Check if there is something that forbids the specific filename in apache config file or in a .htaccess inside /mydir:

Code:

<Files myfile.zip>
Deny from all
</Files>

fatherjack · 04-06-2016, 11:18 AM

Yea weird huh?

No luck there either. Also, by moving to an intermediate filename, i.e.:

mv myfile-copy.zip myfile-copy2.zip
mv myfile.zip myfile-copy.zip
mv myfile-copy2.zip myfile.zip

I'm able to make myfile.zip downloadable, and myfile-copy.zip returns 403! Also tried:

ln myfile.zip test.zip

Which creates a hard link to the bad file, and that also returns a 403, so there's something about that file!

bathory · 04-06-2016, 02:29 PM

Since you're using Centos, it could be SELinux. Try

Code:

restorecon -r /var/www/html

and see how it goes

fatherjack · 04-06-2016, 02:52 PM

Great, SELinux is was! I ran restorecon against /var/www/html and both the bad file, and the hard link I created appeared in the listing!

Thanks a bunch for your help Bathory, that was driving me nuts for a while there!

bathory · 04-06-2016, 03:17 PM

Quote:

Originally Posted by fatherjack

Great, SELinux is was! I ran restorecon against /var/www/html and both the bad file, and the hard link I created appeared in the listing!

Thanks a bunch for your help Bathory, that was driving me nuts for a while there!

Glad to see it worked.
You may mark the thread SOLVED from the Thread Tools on top of the page

Cheers

fatherjack · 04-06-2016, 04:01 PM

Sure, will do. Thanks again.