Resulting URL in CFMX Cluster

Question

I'm configuring our first CF Cluster. Up until now we've used
only CF Standard.
Using the many articles and tutorials from Macromedia's web
I've got everything seemingly up and running. However, I've run
into an issue that is probably an easy fix but has eluded me so
far.
We have two application servers clustered and connecting to
an external IIS server.
I set up a cluster of two Jrun servers, each on a different
server. Specific directories on server 1 and server 2 are
d:\CFMX_Server1\
and
d:\CFMX_Server1\
Easy enough. I then install CFMX7 Enterprise to each in a cfm
folder:
d:\CFMX_Server1\cfm\
and
d:\CFMX_Server1\cfm\
In each these folders are the CFIDE, Web-Inf, etc... folders.
My web site(s) are then placed into these directories as
well:
d:\CFMX_Server1\MySite\
and
d:\CFMX_Server1\MySite\
Next, according to MM's articles, I need to reproduce this
folder structure on the web server, which I did
(d:\CFMX_Server1\MySite\), and then I run the Jrun web site config
tool. Everything works fine.
***IMPORTANT***
I have set the site in IIS to point to the directory on the
web server and, what I figure is, the web config tool has told IIS
to actually look for the site, in the same directory, on the
Cluster I have defined on the CF servers.
This works....BUT...
I can only load my site(s) if I use the "cfm" directory in
the URL. For example:
I want "
http://www.mysite.com" to be
directed to "d:\CFMX_Server1\MySite\" in my cluster, but it
doesn't.
I have to use "
http://www.mysite.com/cfm/"
and then it will open the scripts in "d:\CFMX_Server1\MySite\".
I tried re-creating the Cluster and installing CFMX7 directly
to the Jrun directory so that I had:
d:\CFMX_Server1\CFIDE\
d:\CFMX_Server1\WEB-INF\
d:\CFMX_Server1\index.cfm
But this did not work.
How can I set this up so "
http://www.mysite.com" will point
to the correct directory without need to specify the folder CFMX is
installed in?
Hope this made sense :-)

Answer 1

Do you mean you are coding the HTML yourself?
Firefox will interpret links that do not start with a protocol (e.g., http://) (or with //) as being on the same site displaying the page. For links to external sites, make sure to use the full URL starting with the protocol, or at least starting from the //.
Does that fix it?