I got this answer from cloverleaf suport:
I was informed that this is a documented bug, HUBad10240, that will be corrected with the release of Cloverleaf 5.5.
Implementation (for versions with this issue) used tcl lib cURL to overcome this, and send SOAP transactions.
In current releases tcl cURL is part of Cloverleaf, and all work-arounds then become part of the standard code release.
