Ok, I think we've resolved the <cfcache> "Connection Failed" problem
we were having, so I though I'd pass on how we sorted it out. It's
got quite a bit to do with IP address and I can't guarantee my
explanation will be that great, but here goes...
Our Web Server and ColdFusion server are on the same box, it has an
internal IP address, and an external IP given to it through the
firewall Internal is 192.168.10.3, external is 200.200.100.23
(actually both lies but good enough :)
Whenever we connected to the site internally cfcache worked fine and
as expected. But as soon as someone tried to connect from outside it
all went wrong. Why, well I think it goes something like this...
>From inside, the user requests a page, the cfcache thinks "oh this is
a new one, I'll use cfhhtp to go get it" and used the IP number the
user used to request the page, so cfcache in this case uses the
internal IP address, and finds the page no problem.
>From outside, the user requests a page, DNS points the user to the
external IP number 200.200.100.23, cfcache on the box tries to load
the page by connecting to the IP number used by the external user,
i.e. the coldfusion box tries to connect to 200.200.100.23 doesn't
have a clue where that is, vanishes off through the firewall a couple
of times, does bad network ju-ju and dies.
If cfcache was really nice and lovely it's go "Ah this person is
asking for this file, I'll just look at the local machine which that
file sits on, quite often this one right here" But of course it
doesn't know what to do or where to look.
This is where our techie guys added a couple of lines to the hosts
file (dirve:/winnt/system32/drives/etc/hosts) on the box that
coldFusion and IIS was sitting, so now we have...
----------
# Copyright (c) 1993-1999 Microsoft Corp.
[snip]
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
200.200.100.23 www.the-company.co.uk # public address
192.168.10.3 www.the-company.co.uk # private address
----------
I'm guessing that what happens now is, the external user asks for the
file, cfcache tries to find it on the public IP, fails looks around
for another IP to use, finds the private IP, uses that and
successfully gets the file.
To me, this is all mystic network voodoo, so obviously didn't have a
clue what was going on, and there didn't seem to be any real good
indications for what the problem was. A unencoded version of the
<cfcache> tag would have gone a long way to helping, but never mind.
Hope this helps someone, sorry 'bout the long windedness of the
answer, but I'm too fuzzy to get quick-easy-facts right.
Cheers,
Dan.
This message is intended only for the use of the person(s) ("the intended
recipient(s)") to whom it is addressed.
It may contain information which is privileged and confidential within the meaning of
the applicable law.
If you are not the intended recipient, please contact the sender as soon as possible.
The views expressed in this communication may not necessarily be the views held by
Live Information Systems Limited.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
