On May 7, 2024, we released an updated version of Apigee. Target server SSL enforcement

## Announcement On May 7, 2024, we released an updated version of Apigee. ## Feature **Target server SSL enforcement** With this release, Apigee customers can specify strict SSL southbound enforcement in TargetServer configurations using the object's `enforce` key. If set to `true`, SSL enforcement is applied to service callouts. The option to specify this behavior is analogous to usage of the `<Enforce>` tag in the `<SSLInfo>` block of the TargetEndpoint configuration. For more information, see [Configure strict SSL enforcement ](https://cloud.google.com/apigee/docs/api-platform/deploy/load-balancing-across-backend-servers#configure-strict-ssl-enforcement). ## Feature **Environment-level flag for SSL enforcement** Apigee customers can specify strict SSL southbound enforcement across an Apigee environment, using the `SSLInfo.Enforce` flag. If `SSLInfo.Enforce` is set to `true` or `false`, the value specified overrides any granular enforcement options specified in `<SSLInfo>` blocks in TargetEndpoint or TargetServer configurations. If `SSLInfo.Enforce` is unset, SSL enforcement is determined by any values specified using the `<Enforce>` element within individual `<SSLInfo>` blocks. For more information, see [TLS/SSL TargetEndpoint configuration](https://cloud.google.com/apigee/docs/api-platform/reference/api-proxy-configuration-reference#tlsssltargetendpointconfiguration). ## Feature **Two-way HTTPS health monitor support** Apigee health monitors using `<HTTPMonitor>` can now use all SSL parameters available in the `<SSLInfo>` block of their TargetServer configurations when performing health checks. To enable access, set `<UseTargetServerSSLInfo>` to `true` in the `<Request>` block of the HTTPMonitor configuration. For more information, see [Health monitor using HTTP monitor ](https://cloud.google.com/apigee/docs/api-platform/deploy/load-balancing-across-backend-servers#healthmonitoring-httpmonitor).