title: Laravel 4 controller file name change causing include error
body: <p>I recently deployed a Laravel 4 project on the Web after extensive testing locally, no issues offline but several weird ones after it became live.</p>
  
  <p>The project has a Git repository and one controller would occasionally not be noticed by my IDE (PHPStorm) as being changed in the repository - I would make changes, attempt to commit, and it would show an error saying that there were no changes. Also, at one point the file was somehow renamed to "news.php" from "News.php." I fixed the case of the file back to the uppercase N I did not rename anything else in the project - all references to this class (and therefor file) remained "News."</p>
  
  <p>Out of the blue this morning, a route using the News controller resulted in a 500 error stating that it could not include the file in question. I checked the FTP file system and verified that the file was present and intact, nothing appeared wrong with it at all. After much frustration, I renamed the file to "news.php" (lowercase) and everything worked again. I attempted to rename it to "News.php" again and the 500 error returned.</p>
  
  <p>Another odd thing that happened was that a reference to a controller action was all lowercase (oversight on my part?) and randomly the app crashed with a 500 error Class Not Found. I tested the app locally and it worked fine with either lowercase or uppercase, renaming the controller reference to "Admin_News" from "admin_news" solved the problem on the production server.</p>
  
  <p>Does Laravel 4 have some sort of a cache that might be referencing "news.php" and refusing to use "News.php?" Any ideas on this weird behavior?</p>