Forwarder 1.0.6

All dependencies of the Forwarder are up-to-date and free of vulnerabilities as of the release date.

A custom header x-forwarder-time is added into every proxied request directed to Intelligence Cloud, serving as an indication of the time when the Forwarder proxies VM requests to Intelligence Cloud.

Network communication management between the Forwarder and the VM is improved. Robust network problem handling and comprehensive exchange of detailed information from the Forwarder to the VM has been implemented.

The communication state logged on the VM side now contains this information:

 
[CRS.connection][warning] Request postEventBatch failed on attempt 1 of 3,
elapsed (4,361 ms): code= 502, message=Bad Gateway, payload=null, error=[Forwarder]
The channel for uploading the artifact to Azul Intelligence Cloud has become inactive

This contains more detailed information, compared to the log message in earlier versions of the Forwarder:

 
[CRS.connection][warning] Request postEventBatch failed on attempt 1 of 3,
elapsed (4,361 ms): java.net.SocketException: Unexpected end of file from server

The maximum length of the response content that Intelligence Cloud can send to the VM is increased from 64KB to 512KB. Additionally, you can configure the maximum size of response data that the Forwarder may forward to the Runtimes, thus minimizing potential impact.

See for more details Forwarder Configuring Options.

An issue is fixed where the system lacked the capability to effectively manage certificate-related issues arising from the expiration of the Forwarder certificate. In some cases, such as PC hibernation, the scheduled task of re-issuing the certificate was not executed, resulting in the VM rejecting the SSL handshake, despite the Forwarder functioning properly.