Reading this great article [1] (Thanks Pier!), I realized that the mod_rewrite stuff could possibly be worked around using virtualhosts. I'm not too familliar with Apache HTTPD 2, but I assume setting up vhosts is not much different. Would it not make sense to create a static.domain.com host (if you have the access and resources), and serve up all of your images and resources out of there?
This would allow you to totally ignore the mod_rewrite nastiness. The only problem I could see is having to directly reference static resources with the full domain, for example: <img src="http://static.domain.com/foo.png"/> Then again, it's not all that much different than <img src="/static/foo.png"/> Since they are both absolute paths. Any thoughts on best practices? Tony [1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104441321803644&w=2 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
![http://static.domain.com/foo.png"/](http://static.domain.com/foo.png"/){kind=link}