ACI Server Framework
Many IDOL components are built on the ACI server framework. This section lists the changes in the ACI server layer, which affect all ACI servers.
24.1.0
New Features
There were no new features in this release.
Resolved Issues
-
Sending a long unknown action to an ACI server could cause an interruption of service.
23.4.0
New Features
-
ACI servers no longer reflect a null origin request header in their Access-Control-Allow-Origin response header (in line with W3C guidance).
Resolved Issues
- The
BackupServer
action could fail to backup the datastore files for connector tasks.
23.3.0
New Features
There were no new features in this release.
Resolved Issues
- An IDOL ACI server (running on Linux) would stop if it received a SIGPIPE signal.
- An IDOL ACI server would fail to start if the fully-qualified host name could not be resolved to an IP address.
-
Attempting to POST a large file (larger than 2GB) to an ACI server (for example Media Server) resulted in an error.
23.2.0
New Features
-
IDOL ACI servers now use OpenSSL3 to provide FIPS 140-2 support on both Windows and Linux. This change means that you can run FIPS-enabled IDOL components with the standard component downloads and installers.
For information about how to configure FIPS with these new packages, refer to the FIPS Enablement Technical Note.
NOTE: The FIPS-enabled packages for Red Hat Enterprise Linux (RHEL) 7 and RHEL8 platforms are still available, with the existing configuration. These packages use the system version of OpenSSL (expected to be in the 1.0.x series for RHEL7 and the 1.1.x series for RHEL8).
-
When the
LogEcho
configuration parameter is set toTrue
, components now print license and service errors to stdout, as well as the log file. This change makes it easier to view these errors, particularly when using components in containers.
Resolved Issues
-
Links in the ACI server
GetRequestLog
HTML now work correctly when the server is behind a reverse proxy.