Forwarder 1.0.4

Fixed a performance issue with the connection pool used to connect to the cloud:

The issue occurred when two or more threads attempted to establish a connection to the cloud simultaneously, with distinct index values. One thread was required to wait for the other, even though it was unnecessary, resulting in a delay. This unnecessary wait has been eliminated.

Resolved the problem resulting in a truncated response on the client side, which was caused by an incorrect value in the "Content-length" header when proxied by the Forwarder.

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

Resolved an inconsistent state between the Forwarder state and the detailed metrics utilized for the computation of the state.

Enhanced the Forwarder’s functionality by adding comprehensive explanations in case the Forwarder state is not Green, enabling users to identify and address any issues with greater accuracy.

See Status API for an example.

Resolved an issue concerning the retain/release of HTTP messages that were proxied by the Forwarder, which had the potential to result in memory leaks.

Implemented the feature to periodically monitor and store the status of the Forwarder to a file.

See Forwarder Configuring Options for more information.