API Platform 4.4.0.0

We encountered connectivity problems in the federated gateway because of a bug in the Lettuce library (as the bug is already fixed in newer releases, we have upgraded the Lettuce version used by the gateway).

Calls that contained the header Content-Type coming from the backend with an invalid or duplicate charset were not being logged into the Trace.

The gateway was not accepting requests with the TLS 1.3 protocol if it was configured as both minimum and maximum version in the Inbound Address screen.

The interceptor SQL Threat Protection was not validating all possible injection scenarios and now the regex is more restrictive. If you were using the interceptor in your APIs before, you may experience traffic issues with some data that didn’t use to be barred. You can read more about the interceptor here.

A system configuration related to compressed objects was not working properly, causing the gateway to unpack objects regardless of the settings.