title: Subdomain in .htaccess file only works with index
body: <p>I have a subdomain setup in my <code>.htaccess</code>, which only seems to work with the default <code>index.html</code> page. I'd LIKE it to work for ANY page in the folder corresponding to the subdomain. Edited for privacy, assume my domain is <code>example.org</code>. The pertinent parts of the file look like this...</p>
  <pre><code>#subdomain 
  RewriteCond %{HTTP_HOST} ^subname\.example\.org$ [OR]
  RewriteCond %{HTTP_HOST} ^www\.subname\.example\.org$
  # (a few lines added by my hosting company deleted -- see below)
  RewriteRule ^/?$ &quot;http\:\/\/example\.org\/subname\/&quot; [R=301,L]
  </code></pre>
  <p>So the result of the above is that if I have an <code>index.html</code> page in my 'public-html' (root?), <code>http://example.org</code> and a different <code>index.html</code> stored in a sub-folder (having the same name as the subdomain), I will get this expected result, which works...</p>
  <p>browse to: <code>http://example.org</code>  results in viewing <code>http:// example.org/index.html</code><br />
  browse to: <code>http://subname.example.org</code> results in viewing <code>http:// example.org/subname/index.html</code></p>
  <p>Great so far. This is what I expected when I created the domain name. However, given a specific file <code>myfile.html</code> stored in the <code>subname</code> folder, I would expect this to work also, and it doesn't...</p>
  <p>browse to: <code>http://subname.example.org/myfile.html</code> results in a 404 error.</p>
  <p>This despite the fact that browsing to <code>http://example.org/subname/myfile.html</code> works fine. In that case <code>myfile.html</code> is displayed. So is there anything I can do to modify the subdomain code to get the result I'm looking for? Namely, browsing to <code>http://subname.example.org/ANYFILE</code> should work as well as browsing to <code>http://example.org/subname/ANYFILE</code>, regardless of what 'ANYFILE' is. This, after all, is one of the main reasons I set up the subdomain to begin with!</p>
  <p>Note: I confess that I relied on my hosting company's cPanel utility to create the subdomain code, so I asked for their tech support for help first. Long story short they didn't. Maybe what I hoped for is not actually possible?</p>
  <p>Also, the lines I deleted' from the code had to do with something called &quot;well-known/acme-challenge&quot;, added by my hosting company at some point. Since removing them had no effect on the behavior I've described, I left it out to avoid clouding the issue.</p>