Thanks for your help, but the "http_server" section is used to allow a WS EMS to accept local calls from the machine or device code that may be running in a different process, such as the Lua Script Resource:
Our problem is the connection between the EMS and the Thingworx server. If the connection is secure (insecure communication works well) the EMS is unable to communicate with Thingworx server 8.0.
We believe that the problem is in the configuration of the Thingworx Server.
This is the log of the web server:
[Wed Jul 12 16:20:32.728432 2017] [ssl:debug] [pid 10980:tid 139647757801216] ssl_engine_kernel.c(570): [client 192.168.3.110:51304] AH02255: Changed client verification type will force renegotiation
[Wed Jul 12 16:20:32.728445 2017] [ssl:info] [pid 10980:tid 139647757801216] [client 192.168.3.110:51304] AH02221: Requesting connection re-negotiation
[Wed Jul 12 16:20:32.728462 2017] [ssl:debug] [pid 10980:tid 139647757801216] ssl_engine_kernel.c(770): [client 192.168.3.110:51304] AH02260: Performing full renegotiation: complete handshake protocol (cli
ent does not support secure renegotiation)
[Wed Jul 12 16:20:32.728530 2017] [ssl:error] [pid 10980:tid 139647757801216] [client 192.168.3.110:51304] AH02225: Re-negotiation request failed
[Wed Jul 12 16:20:32.728608 2017] [ssl:error] [pid 10980:tid 139647757801216] SSL Library Error: error:14080152:SSL routines:SSL3_ACCEPT:unsafe legacy renegotiation disabled
And this a screenshot of the TCP trace: