Hey guys,
We were thinking about enabling http compression for the static files of our site (IIS 5.0).Actually the static files, are not .htm nor are they .html files. They're .cfm, Cold Fusion files. The question is, if I set the IIS server to handle .cfm pages as static files, would I mess something dynamic in the site? Meanwhile, full dynamic shopping carts, or secured sessions, etc ?
e.g. Now, this URL is unique which will expire after one opens it up, if it were to be cached in IIS, I'm guessing there is a possibility that this unique token might be viewed by someone else ?? [ or am I being too stupid?]
We have a lot of static pages that ends with .cfm which the server should cache, but we also have dynamic pages in the site, where I don't want to get any trouble as I stated above.
Any ideas about this ? would it be a problem?
Thanks in advance.
We were thinking about enabling http compression for the static files of our site (IIS 5.0).Actually the static files, are not .htm nor are they .html files. They're .cfm, Cold Fusion files. The question is, if I set the IIS server to handle .cfm pages as static files, would I mess something dynamic in the site? Meanwhile, full dynamic shopping carts, or secured sessions, etc ?
e.g. Now, this URL is unique which will expire after one opens it up, if it were to be cached in IIS, I'm guessing there is a possibility that this unique token might be viewed by someone else ?? [ or am I being too stupid?]
We have a lot of static pages that ends with .cfm which the server should cache, but we also have dynamic pages in the site, where I don't want to get any trouble as I stated above.
Any ideas about this ? would it be a problem?
Thanks in advance.
