On windows 2000, CFHTTP seems to be causing the CF service to hang. I've
had intermittent problems since a application using CFHTTP extensively was
put onto the server. Server is Win2000 Server, with CF 4.5.2. I'm pretty
sure CFHTTP is the cause of the problem because in addition to the problems
only starting since the app using CFHTTP went live, I'm also now logging
every request for a .cfm and the last .cfm to be requested is always one
containing a CFHTTP call. Unfortunately, I haven't been logging any
performance counters until now and there hasn't been a CF failure in about
5 days so I've not further info at the moment.
My question - does anyone know how the internals of CFHTTP work on Windows?
Does it use the wininet.dll? I've never had these problems before using
win2000, and I noticed that on a working NT 4.0 installation (also w. CF
4.5.2) which heavily uses CFHTTP for importing syndicated content, there is
a copy of the wininet.dll in the CFUSION\BIN directory. This file was not
copied across on the Win2000 installation, presumably because a later
version was found in WINDOWS\SYSTEM32. I wonder if I copied the version of
wininet.dll which came with CF on the NT machine to the same directory on
the win2000 server, would CFHTTP load this library instead of the one in
WINDOWS\SYSTEM32 and would it then work without problems? I don't want to
do this without a lot of testing, but I'm outta time - I've a new app using
CFHTTP which is likely to be heavily hit ready and it's supposed to go live
tomorrow. I'm really worried about putting this live without resolving the
intermittent problems with the service hanging. Has anyone else had similar
problems with CFHTTP on Win2000?
BTW, cfx_http is not a suitable replacement for cfhttp in this case.
Oh, I should point out that I have moved the app onto a Linux server
temporarily, but apart from CF on Linux being dog slow at string parsing,
I've also run into some minor CFHTTP problems there too. CFHTTP often
sticks the port into the resolved URL and worse, resolves some relative img
src attributes by just putting http:// before the relative path (no server
name). One of the worst examples were relative paths to images in a
directory which resolved from say src="pix/news/logo.gif" to
src="http://pix:80/news/logo.gif". I doubt there is any way around this as
it seems to be just a bug with CFHTTP. With this in mind and the fact that
I've found CF on Linux to be very slow at string parsing, I'd really like
to get the problems on the win2000 server sorted ASAP (that NT4 server is
owned by another company).
Mark
(PS, my apologies for the length of this message - anyone who gets as far
as reading this bit, thanks for reading even if you have been unable to help)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
