MTE Relay Server v4.1 Release Notes

MTE Relay Server v4.1 improves deployment flexibility and makes proxy behavior more reliable across both successful and error responses.

The release also simplifies configurations that do not need browser CORS support and improves request tracing while debugging.

New

• Optional CORS origins. corsOrigins is no longer required. Deployments that do not need browser cross-origin support, such as server-to-server setups, can omit it entirely.
• Debug request-ID response header. When debug mode is enabled, the server adds the request ID to the response as a header, making it easier to correlate client-side activity with server logs.

Changed

• More reliable proxying. The proxy path was reworked so that the upstream HTTP status code is preserved on the way back to the client, and error responses are encoded and decoded just like successful ones.
• Redirect handling. Redirect responses from the upstream application are now handled correctly through the relay.