Skip to content

Commit 639bce0

Browse files
committed
Merge branch 'patch-7' of https://github.com/Vignesh-Microsoft/azure-docs into fxl---Update-best-practices-107162
2 parents d4cf80a + 9637226 commit 639bce0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-cache-for-redis/cache-best-practices-development.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ Microsoft is updating Azure services to use TLS server certificates from a diffe
110110
111111
#### Does this change affect me?
112112

113-
We expect that most Azure Cache for Redis customers aren't affected by the change. Your application may be impacted if it explicitly specifies a list of acceptable certificates, a practice known as “certificate pinning”. If it's pinned to an intermediate or leaf certificate instead of the Baltimore CyberTrust Root, you should **take immediate actions** to change the certificate configuration.
113+
We expect that most Azure Cache for Redis customers aren't affected by the change. Your application may be impacted if it explicitly specifies a list of acceptable certificates, a practice known as “certificate pinning”. If it's pinned to an intermediate or leaf certificate instead of the Baltimore CyberTrust Root, you should **take immediate actions** to change the certificate configuration. On a side note, Azure Cache for Redis doesn't support [OCSP](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-ocsp/5792b4c4-c6ba-439a-9c2a-52867d12fb66) either.
114114

115115
The following table provides information about the certificates that are being rolled. Depending on which certificate your application uses, you might need to update it to prevent loss of connectivity to your Azure Cache for Redis instance.
116116

0 commit comments

Comments
 (0)