cfhttp trace logging doesn't log connection failures

Description

for example, an invalid hostname or unknown host (offline), etc doesn’t get logged

to reproduce,

  1. setting trace.log to info,

  2. execute <cfhttp url="https://www.lucee11.org" method="post" charset="utf-8">

expected result, something along the lines of

"httpRequest [POST] to [https://www.lucee11.org], returned [0 Connection Failure] in 352ms, at C:\lucee\tomcat\webapps\index.cfm:6"

  1. POST,https://www.lucee111.org

Environment

None

relates to

Activity

Pothys - MitrahSoft 
31 October 2022 at 13:34

I've checked this ticket with the lucee latest build 5.3.10.87-SNAPSHOT & 6.0.0.278-SNAPSHOT. Now the cfhttp trace logging logs connection failures.

Zac Spitzer 
28 October 2022 at 14:47
(edited)

Pothys - MitrahSoft 
19 October 2022 at 07:07

I've checked this ticket and confirmed the issue happened on the lucee latest version 5.3.10.84-SNAPSHOT. cfhttp connection failures due to the unknown host and request time out are not logged into the trace log.

I added a fix to this ticket
PR for 6.0:
PR for 5.3:

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Created 17 October 2022 at 13:11
Updated 31 October 2022 at 13:34
Resolved 31 October 2022 at 13:34