When invoking cfhttp with the "timeout" attribute, its effective timeout is calculated depending on the remaining available time for the current page, instead of applying the specified timeout value directly.
This makes kind of sense, but can be very confusing for developers. I suggest altering the error message returned upon a cfhttp connection timeout.
Behind the scenes, cfhttp is given a connection timeout of about 3 seconds since that's what remains after 7 seconds of execution time, regarding the page timeout of 10 seconds.
So if slowhost.example.org takes more than those 3 seconds to respond, a "Connection timeout" will be returned by cfhttp.
If (in complex projects) the developer isn't aware of the total page timeout and of the timeout calculations taking place behind the scenes, they will try to increase the "timeout" attribute for cfhttp, but to no avail.
It would be nice if the resulting error message contained a hint regarding the page timeout instead of just reading "Connection timeout", if the effective connection timeout has previously been shortened to honor the page timeout.