title: Simple mod_rewrite rules broken after new c9 version
body: <p>I'm working on a project hosted on the <a href="http://c9.io" rel="nofollow">Cloud9 IDE</a>. I had a simple set of mod_rewrite rules set up, but they no longer work after c9's new version rollout. It took me forever to iron out these rules (I'm a novice at best at this) I'm confused as to why these rules no longer work (AFAIK, the new c9 version should not have affected mod_rewrite rules).</p>
  
  <p>Here are the rules (located in the root <code>.htaccess</code>)</p>
  
  <pre><code>RewriteEngine on
  Options FollowSymLinks
  
  RewriteBase /
  
  RewriteCond %{REQUEST_URI} ^/css/.*$ [OR]
  RewriteCond %{REQUEST_URI} ^/img/.*$ [OR]
  RewriteCond %{REQUEST_URI} ^/js/.*$
  RewriteCond Astralis/resources%{REQUEST_URI} -f
  RewriteRule ^(.+)$ Astralis/resources/$1 [L,QSA]
  
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule ^ index.php [L]
  </code></pre>
  
  <p>The goal is pretty straightforward... All requests going to <code>/css/...</code> <code>/img/...</code> or <code>/js/...</code> should serve up the associated file within <code>Astralis/resources</code> (after checking that the file exists). Otherwise, redirect the rest of the traffic to index.php.</p>
  
  <p>The problem I am experiencing is that all requests to resources (css, img, js) are returning 404's. If I move the /css, /img, and /js folders from within Astralis/resources back to the root directory, all the resources load properly. This problem started happening after c9's new version, with no changes to the .htaccess file, the codebase, or directory structure.</p>
  
  <p>Any clue as to what is going on? How do I debug this kind of stuff? Any general tips/tricks for writing mod_rewrite rules would also be appreciated. Thanks.</p>