AWS lightsail documentation change
Summary
Clarified HTTPS configuration options for WordPress distributions, specifically rewording explanations about HTTP-only and HTTPS origin configurations
Security assessment
The changes are editorial improvements to existing HTTPS documentation without addressing vulnerabilities or adding new security features. They clarify existing security configurations but don't reference any security incidents or introduce new protections.
Diff
diff --git a/lightsail/latest/userguide/amazon-lightsail-configure-wordpress-for-distribution.md b/lightsail/latest/userguide/amazon-lightsail-configure-wordpress-for-distribution.md index 3120c4562..c3891931a 100644 --- a//lightsail/latest/userguide/amazon-lightsail-configure-wordpress-for-distribution.md +++ b//lightsail/latest/userguide/amazon-lightsail-configure-wordpress-for-distribution.md @@ -15 +15 @@ All Lightsail distributions have HTTPS enabled by default for their default doma - * Your WordPress website uses HTTP only – If your website uses HTTP only as the origin of your distribution, and it is not configured to use HTTPS, you can configure your distribution to terminate SSL/TLS and forward all content requests to your instance using an unencrypted connection. + * Your WordPress website uses HTTP only – If your website uses HTTP only and is not configured for HTTPS, you can configure your distribution to terminate SSL/TLS. The distribution forwards all content requests to your instance using an unencrypted connection. @@ -17 +17 @@ All Lightsail distributions have HTTPS enabled by default for their default doma - * Your WordPress website uses HTTPS – If your website uses HTTPS as the origin of your distribution, you can configure your distribution to forward all content requests to your instance using an encrypted connection. This configuration is known as end-to-end encryption. + * Your WordPress website uses HTTPS – If your website uses HTTPS as the origin, you can configure your distribution to forward all content requests to your instance using an encrypted connection. This configuration is known as end-to-end encryption.