Version 23.08-01 August 25, 2023

Enhances the datapath to generate a session summary event when the gateway connection and proxy timers are exceeded. This enhancement will help in troubleshooting when a session is closed by the gateway due to timer settings.

Enhances the gorward proxy service object to accommodate L4 (TCP) and L5 (TLS) proxies. This is achieved by specifying either TCP or TLS as a valid value for the transport_mode argument.

Enhances the gateway datapath to track session performance.

Enhances the gateway datapath process to generate a TCP reset to actively close the connections during a datapath restart.

Fixes an issue where URL encoded characters of [ and ] in an HTTP object name where decoded by the gateway, but not re-encoded before sending the request to the server. This results in the server not being able to properly locate the object, returning a 400 response code. This fix properly re-encodes the characters prior to sending the request to the server.

Fixes an issue where the presence of underscores in an SNI would cause the proxy to not pass traffic. This change enables the proxy configuration to accommodate the use of underscores in domain names.

Fixes an issue where traffic is matched to a correct policy, but an incorrect certificate is issued.

Fixes an issue where traffic is matched to a correct policy, but an incorrect certificate is issued.

Fixes an issue with large file transfers related to HTTP commands (e.g., Github repository cloning) where a proxy timeout would result in a 408 status code.

Fixes an issue where URL Filtering category query timeout expires causing the traffic to be denied.

Fixes a stability issue with the ingress gateway where the datapath could self heal due to an issue with the upstream proxy.

Fixes an issue where the gateway could introduce additional latency when processing certain types of traffic.

Fixes an unnecessary datapath restart that is triggered when enabling memory profiling.

Fixes an issue where the gateway could intermittently generate a 502 due to a datapath restart triggered by a policy change.

Fixes an issue with CPU-based auto-scale could result in an unnecessary scale out.

Fixes a proxy connection leak.

Improvements to the stability of the Multicloud Defense Gateway.