I'm not talking about Cross-Contamination script but something totally different.
Files on one site are being shown on a totally different site (on the same sever but differently defined IIS sites), from separate directories, causing confusion and lots of trouble.
We have a dozen sites defined in IIS 8.5 and using ColdFusion 11.
Some of the sites are similar and use the same folder and file names. Each defined site in IIS8.5 has a different home directory off C:\inetpub\wwwroot. All files for each site resides in separate folders so I don't understand why one site would be displaying files from another website. Example:
The directory "news" and it's file: article1.cfm reside off the root for each site, as you can see. All sites are on the same network and the same server, same Windows Server 2012r2.
However, each article1.cfm is a page that contains different content on each site, and of course, different domain names so it's embarrassing to have one site show the contents of the other site to our viewers. I realize I need to keep the content separate but the sites are so similar that it's easy and convenient to use the same cf code from one to another.
To sort of solve and keep one site from using the same files, I'm forced to change the news folder names AND the article1.cfm names of each page.
I've even made certain that the file link on each site where there is a problem, using the full domain name and the file path. But that does not help at all. And CACHE is turned off.
All sites share some of the same SQL 2008 R2 databases.
Or create a mapping in CF Administrator and mark code for every instance so there is no cross site contamination. I also try to keep the default document different for each site's home page.
But that's a lot of work and I'm hoping ColdFusion has a better and more efficient method of keeping each site separate, even when they have identical folder names and files, and that someone will point this out and how to implement it.
So, not sure if this is a CF or an IIS problem. Also wondering why this happens when each site points to a totally different and separate path.