top of page


WAARP news

WAARP R66 3.4.0

Second major iteration

Waarp R66 Update Release Notes

For starters, Waarp R66 version 3.4.0 is the second major iteration of Waarp R66 since the start of the year. It thus brings two new functionalities:

  • First of all, support for the ICAP protocol to deport certain checks of files transferred to compatible servers

  • Then adding a unique identifier associated with the file transferred and kept from bounce to bounce (followId)

Also, it includes several developments, fixes, and optimization of the use of system resources.

ICAP Support

In addition, a new task called ICAP has been created to allow exchange with a server meeting the RFC 3507 standard called ICAP. It allows you to transfer the contents of the file to an ICAP service via a RESPMOD command and to obtain validation of this file by the service.

Thus, this task can be used for example to perform antivirus checks on files, or for other security filtering using ICAP compatible servers.

Moreover, consult the documentation to find out more by clicking here .

Follow ID

Then, regarding transfers, a new functionality allows you to manage fine monitoring of retransfers (rebounds between several R66 servers). This option positions a field in the transfer information part of the following form: {"follow": numeroUnique} for the first transfer and subsequent transfers will thus retrieve this information natively.

Note that this option is active by default, so to deactivate it, you must specify the -nofollow option.

Finally, the REST v2 interface includes the search option by followId (GET /v2/transfers/?followId=number). number being possibly a long integer, it is recommended to manipulate it as a character string.

Reduction of startup logs

You should know that initializing the log writing library sometimes generates logs at startup which can be avoided (by retaining warnings and errors) by adding the following parameters to the logback.xml configuration file. head of options:

<statusListener class="org.waarp.common.logging.PrintOnlyWarningLogbackStatusListener" />

Default configuration

In order to optimize data transfers and the use of system resources, the default values of certain configuration options have been modified:

  • First, the default global bandwidth usage limit (globallimit option) is increased to 100 Gbps.

  • Then, the global bandwidth usage limit per connection (sessionlimit option) is increased to 1 Gbps.

  • And finally, the default value of the maximum RAM used by WEB and REST services has been lowered to 1 GB (instead of 4 GB).

These changes are accompanied by numerous optimizations in RAM usage.

List of changes

What's new

  • Assigning a tracking ID to transfers

  • The REST v2 interface includes the option to search by tracking ID

  • ICAP support

  • Increasing bandwidth limitations by default.

  • The reduction in RAM used by the HTTP and REST services of Waarp R66 servers.

  • The possibility of deleting the initialization logs from the log writing library

  • The reduction in the memory footprint for the case of simple clients and reduction in server-side memory for the Web and REST parts.

  • And so, if no -Xms argument is passed to the JVM during startup, the default value of the JVM applies (generally 4GB).

  • Then, correct support for regular expression filtering in the file watcher (it was impossible to filter just on the name of a file located in a subfolder).

  • Some commands no longer worked due to a bug in the logs.

  • Updating external dependencies


To conclude, this new version is completely compatible with versions 3.x and does not require any special handling for the update.

So the standard procedure can be followed.



bottom of page