Appwrite 1.4.0 TLS hostname verification change for custom domains

When upgrading a self‑hosted Appwrite deployment from version 1.3.x to 1.4.x, administrators need to know whether the platform still accepts TLS certificates that rely only on a Common Name (CN) match when no Subject Alternative Name (SAN) is present. The 1.4.0 release notes indicate that strict hostname verification was introduced and that the fallback to CN matching was left unresolved, creating uncertainty about the exact validation behavior for existing certificates.

• Does Appwrite 1.4.x continue to fall back to CN verification when a certificate lacks a matching SAN?
• If the fallback is removed, what steps are required to maintain compatibility with existing CN‑only certificates?
• Is the _APP_WRITE_ENABLE_SSL_VERIFICATION environment variable the only reliable way to control this behavior?