404 on some files

Question

Is there anything in EE that would cause some files under web root to be accessible while others return a 404?

For example, I have a /js/ with about 10 JS files. About 8 of them are accessible, but the other 2 returns a 404 error (I have verified that the files do exist on the server). Same with my /cache/ folder (where Minimee files are saved); the generated files are returning 404.

UPDATE 1:

Here's the screen shot of the error I am getting:

It's an EE error page, so this has to do with EE somehow, right?

UPDATE 2: Directory listing of /js/

As I am just clicking on these links that are produced as a result of Apache's directory listing, I am not inclined to believe that I am running into any case sensitivity issues. The two unvisited links are the ones returning 404s.

Answer 1

First thing to check is your .htaccess file.

Remove everything in it and use the code sample provided by EllisLab in the docs for removing index.php: https://ellislab.com/expressionengine/user-guide/urls/remove_index.php.html

<IfModule mod_rewrite.c>
        RewriteEngine On
        RewriteBase /

        # Removes index.php from ExpressionEngine URLs
        RewriteCond %{THE_REQUEST} ^GET.*index\.php [NC]
        RewriteCond %{REQUEST_URI} !/system/.* [NC]
        RewriteRule (.*?)index\.php/*(.*) /$1$2 [R=301,NE,L]

        # Directs all EE web requests through the site index file
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ /index.php/$1 [L]
</IfModule>

Answer 2

First, look at your htaccess file. It looks like you're able to access other files with a .js extension, so your javascript folder is probably ok. You might just be setting your file path to a file that isn't case-sensitive correct.

Keep in mind that different operating systems handle case sensitivity differently. On OS X, files are case insensitive (same goes on Windows), while on Linux, files ARE case sensitive. So, filename.js and FileName.js are 2 different files on Linux.

Answer 3

I know you have your answer but it can be useful to ls -al and check permissions/ownership on the files too - if you're managing your own server it can be persissions/groups issues that cause these errors too. just adding this as another tool in the toolbox :)