This document contains New Features, Important Enhancements, Modifications and Bug Fixes for version 2025.01.1.

New Features

Apinizer Trino Connector support has been added.

Important Enhancements and Modifications

APNZ-4870 When 'Global Setting' is active in Connection Settings, access to the relevant 'Global Setting' is provided.

APNZ-4872 While searching by method in the API Traffic screen, the communication protocol of the method is added as a label.

APNZ-4875 In endpoint settings, it is now possible to leave the 'Path (of Backend API)' value blank.

APNZ-4877 To allow the requestBackendUrlToTargetAPI value to be empty, the value #EMPTY# can be used.

When this value is used, the request is routed directly to the routing address without any path or query added.

APNZ-4881 The ability to add a logo to the API Portal has been provided.

Issue No	Description
APNZ-4862	When downloading the OpenAPI file in the API Portal, it gets blocked by the WAF rule and throws an error.
APNZ-4863	A namespace mismatch occurs when Apinizer Manager is deployed to a namespace other than the Apinizer namespace.
APNZ-4878	If the Content-Type of form-data is not specified as octet-stream, text files are sent as text instead of files.
APNZ-4879	When names are changed during worker deployment, probes or service objects are inaccessible despite the pod running.
APNZ-4869	The start time of WebSocket messages is recorded as the session start time.
APNZ-4871	In HTTP type API proxies, the 'PICK First' algorithm is used in Routing Algorithms.
APNZ-4873	The 'Error Response Template' is not automatically activated according to the API's SOAP or REST type.
APNZ-4874	The text area view shifts behind the HTML element.
APNZ-4876	A null error is encountered during import for API proxies without a spec.
APNZ-4882	When the Apinizer root context is empty, the API Proxy cannot be found during WebSocket access.
APNZ-4883	pfx extension keystore and truststore cannot be uploaded in the Environment screens.