I have multiple sites on my coldfusion webserver. I want to make a new site that does not allow coldfusion to run. At the same time I do not want to disable coldfusion on the other sites.
I am running coldfusion standard edition.
A:
Which webserver? If you run standard standalone installation I'm afraid you can't do that without digging into deep dark places of configuration files. If it's IIS or Apache or whatever, than it's possible.
zarko.susnjar
2010-06-24 14:14:32
I'm running this in IIS.
Brian Bolton
2010-06-24 15:51:56
IIS which version? 6? 7?
Henry
2010-06-24 18:14:43
+2
A:
Like Zarko said - What webserver are you referring to? If it's ColdFusion's own application server (JRun) then you've got a difficult task here.
If you're running things through a webserver, like IIS or Apache, before hitting CF then the simplest thing to do is not create files with the .cfm, .cfc etc. extensions on them.
Use HTML instead OR remove the JRun Connections from the website / host that is going to be running this other site.
--
Same applies for it you want to run other languages like PHP off the same server. Tell the webserver which drivers to use for which site and it'll pass the request onto the correct application server to be processed.
James Buckingham
2010-06-24 14:20:21
in addition to what James suggested, I would also setup a filter for the site in question, and have it watch for requests to ".cfm" and ".cfc" and redirect the browser to a different page. You'll want to have that filter before the coldfusion filter.
Jay
2010-06-24 14:45:02
A:
Even simpler, just do not use any cfml code or create any new datasources for the other sites.
Just don't use any coldfusion code for your other site.
Or you can disable the http handler's for coldfusion for this other site.
But if this other site does not include any .cfc or .cfm files than that is not a coldfusion site. That's all there to it.
Why does it matter?
crosenblum
2010-06-24 21:50:27
I can think of several instances where I might want to disable CF on one site. For example, in a small hosting company, you might disable CF on specific sites to prevent users from using it on static site packages.
Ben Doom
2010-06-25 21:08:49
+10
A:
In IIS, find the Application Configuration Window where all the extensions are listed and which Executable they are linked to.
Just delete the one for .cfm and any other extension that links to the Cold Fusion dll
Ed B
2010-06-24 22:02:17
+1
A:
The other thing to watch out for is the CFIDE virtual directory. This won't be a problem if you create a new site from scratch, but if your disabling CF on an existing site you should remove the virtual directory.
tHeSmUrF
2010-07-01 01:31:56