10.4. What’s Fixed in 7.3.0 LTS

This section describes bugs fixed in Web Integration Service 7.3.0 LTS. These are fixes applied since 7.2.0.

For information on what was fixed in releases 7.0.0, 7.1.0, and 7.2.0, which are also part of 7.3.0 LTS, see Previous Releases.

[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.

10.4.1. Crashes

10.4.1.1. [Critical] Web Integration Service crashed when invalid file used as -aclFile argument

Web Integration Service did not handle exceptions properly on encountering invalid access control files, causing the service to crash.

Now, exception messages will be printed.

[RTI Issue ID WEBINT-302]

10.4.1.2. [Critical] Crash when parsing invalid HTTP requests

Web Integration Service did not handle exceptions properly when attempting to parse invalid HTTP requests in XML. Web Integration Service supports XML and JSON formats. When there is no content type defined, the default is XML; if sending JSON, the content type must be defined.

Improper exception handling caused the service to crash, specifically during the HTTP request to /dds/v1/websocket_connections.

[RTI Issue ID WEBINT-316]

10.4.2. Data Corruption

10.4.2.1. [Critical] Memory corruption when writing samples using JSON Websocket API in Web Integration Service

Writing samples using the JSON Websocket API, in a connection with Content-Type=application/dds-web+json, when some of the data in a sample had fewer characters than the previous sample, triggered a memory corruption.

[RTI Issue ID WEBINT-321]

10.4.2.2. [Critical] Bind ID sent to all websocket connections was same as first connection bound to DataReader

New received samples are sent to bound connections with a message. An optimization that creates the message only once resulted in always sending the same bind ID to all the bound connections.

[RTI Issue ID WEBINT-324]

10.4.3. Other

10.4.3.1. [Critical] Removing Web Integration Service library instance destroyed external DomainParticipants *

When Web Integration Service was used as a library, all external DomainParticipants not created with the Modern C++ API were destroyed when the Web Integration Service library instance was removed.

[RTI Issue ID WEBINT-311]

10.4.3.2. [Major] Partial CORS support in Web Integration Service *

Web Integration Service as a library included partial support for CORS (Cross-Origin Resource Sharing). Now CORS support is complete, and the executable also has CORS support through the use of three new command-line arguments:

-accessControlAllowHeaders: Sets the allowed headers
-accessControlAllowMethods: Sets the allowed methods
-accessControlAllowOrigin: Sets the allowed origin

For more information, see Command-Line Parameters.

[RTI Issue ID WEBINT-215]

* This bug does not affect you if you are upgrading from 6.1.x or earlier.