Crosser Node 2.5.5 - Enhanced proxy support and critical patches

Bugfix - Enable *_PROXY Usage

Previously the Crosser Node only supported HTTP_PROXY/HTTPS_PROXY, but as of v2.5.5 the list below is supported.

The environment variables used for DefaultProxy initialization on Windows and Unix-based platforms are:

• HTTP_PROXY: the proxy server used on HTTP requests.
• HTTPS_PROXY: the proxy server used on HTTPS requests.
• ALL_PROXY: the proxy server used on HTTP and/or HTTPS requests in case HTTP_PROXY and/or HTTPS_PROXY are not defined.
• NO_PROXY: a comma-separated list of hostnames that should be excluded from proxying.

Bugfix - MQTT Large Payload Issue

When publishing large messages there was a risk that you would loose data in the message.

This issue was introduced in v2.5.4 and corrected in v2.5.5

Bugfix - MQTT Disconnect Issue

MQTT connection would be disconnected (and then reconnected) on an interval of 45 seconds.

This issue was introduced in v2.5.4 and corrected in v2.5.5

Bugfix - HTTP Large Payload Issue

When posting large messages there was a risk that you would loose data in the message.

This issue was introduced in v2.5.4 and corrected in v2.5.5

Change - Prevent Debug of Large Payloads in Remote Session

Since the browser may crash if we try to display very large messages in a remote session we now prevent large amounts of data to be sent to the UI in a remote session. The limit is 100.000 bytes.

If that limit is crossed you will instead see a message like this:

{
  "Information": "Payload too large to display"
}