On Wednesday 19 March 2003 04:14, Tony Collen wrote: > 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?
I, personally, don't like having related content on separate hostnames (I don't like rewrites for same reason). The links becomes more prone to errors, especially in a mixed environment. If I don't have hosts (or depending on rewrites) in the links, I can setup offline environments which works (at least to a great degree), improving testability by the author. Niclas
![http://static.domain.com/foo.png"/](http://static.domain.com/foo.png"/){kind=link}