I read articles about website acceleration by providing static cookieless content. We have an ASP.NET site with links to images / css / js, for example
<script type="text/javascript" src="/js/something.js"></script>
I tested the static content filter from this article and it seems to work fine for situations like the ones described above. However, we also have many CSS files with styles such as:
background-image: url(/images/something.jpg)
The static content filter will not work for these situations. Since there are many of our image locations in our CSS files, is there a good way around this?
Whenever a project is uploaded to our local development machines, we obviously want all the files to be sent from localhost, so we cannot hardcode all of these locations.
Is there another solution or is there something we can change to make this work?
source
share