| |||||||||||||||||||||||||||||||||||||||||||||||||
First, my profuse thanks go out to Steven Erat. He discovered a solution to a problem that had been plaguing me for over a month.
When Ping-o-Matic launched, I switched JournURL's auto-pinging code to them from Weblogs.com. And all was well for the first month or two, until P-o-M upgraded to a new server... poof, overnight, we went from successful pings to "Connection failure". And when I ran into the exact same problem when trying to help beta test Syndic8's ping service, I got concerned.
On the surface, it seemed as if it might be some kind of host header problem, so I tweaked in that area. Then I tried encodings. Nothing worked. I finally surrendered a couple weeks ago and started using MSXML, which worked, but not reliably.
So when I finally dug Steven's entry out of the "to read" pile and implemented his work-around, I was thrilled to see immediate success. And I can now pass along a few extra bits of info gleaned from my experience.
- This definitely isn't an IIS-specific problem, at least not on the receiving end. Both of the servers that caused me trouble are running Apache.
- It doesn't appear to be an issue with most default Apache installs, because I have not seen the problem prior to the last few months.
- The client OS seems to factor into the process somehow. My MX6.1/Win2003 production box was choking, but my MX6.1/Win2000 dev box could connect to the problematic sites with ease, using identical code.
TalkingTree.com - Entries for July 29, 2004
Some versions of IIS may use an HTTPCompression algorithm that is incompatible with ColdFusion (or Java in general). When using CFHTTP to performthe operations GET or POSTon the target website, if the target site is using Microsoft IIS with HTTP Compression enabled, the CFHTTP tag may report a Connection Failure.08-26-2004 07:43:10PM - Permalink - Comment [0] - Trackback
category: General
related topics: (Steven Erat) (ColdFusion) (MX) (CFHTTP) (Gzip) (Apache) (IIS) (Connection Failure)