This would likely be better understood if an example was provided.
I’d like to see what you’re doing with your RewriteRule and the method you are trying to use to backreference variables from your RewriteConds. It may be as simple as changing the %1 to a $1, however you have only confirmed that you know the syntax of RewriteCond, not the methods you are using for pattern matching.
I supposed that could be interpreted a couple of different ways but your experience shows only one: Only the last RewriteCond’s atoms are retained for the RewriteRule (and it’s references cannot be "backreferenced by earlier RewriteCond statements). Of course, you can create an environmental variable with a [E=VAR:VAL] flag, too.
You’re trying to condense your rewrite too much. You can’t back-reference to the first RewriteCond (reference1), only the RewriteCond before (reference2).
I recommend keeping the first RewriteCond with the %{HTTP_HOST} and putting the ${REQUEST_URI} within the RewriteRule Test.
The RewriteRule would look something like…
RewriteCond %{HTTP_HOST} ^(acp|clients|files|images|ssl|www)\.([-a-z0-9]+) [NC]
RewriteRule ^/(.*).(css|jpg|gif|png|js)$ /%1/index\.cfm?good [L]
I hope that this is correct, I’m away from any servers for testing. Are you wanting to use the css, jpg, etc. extensions anywhere?
My current issue is that when the page code is created, if you’re familiar with HTML code, there is a BASE tag with an HREF attribute. I have one of 2 options:
I like option 1 better because it specifies the subdomain (which is the folder under the site root). With option 1, relative links like <img src=“ui/images/file.png”> would equal http://www.aaronmartonecom/ui/images/file.png. I would need the URL rewrite to see this URL and call “c:/inetpub/wwwroot/aaronmartonecom/www/ui/images/file.png” If I can do this, all is well. Links to pages like <a href=“about”>About</a> would goto http://www.aaronmartonecom/about" and the rewrite would determine that this doesn’t exist so it would request c:/inetpub/wwwroot/aaronmartonecom/www/index.cfm?$ses=/about
With option 2, the problem is that a relative link like <a href=“about”>About</a> would link then to http://www.aaronmartonecom/www/about (which is wrong, I want it to request http://www.aaronmartonecom/about, which would then call c:/inetpub/wwwroot/aaronmartonecom/www/index.cfm?$ses=/about
Sure, I could make sure that everyone of my links uses ABSOLUTE linking to avoid this, but I don’t want to settle for second place.