From 9dee1a12fb804535402003fb7ba8a68ec3a1a941 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Wed, 15 Nov 2017 16:05:11 -0800 Subject: [PATCH] Changes so content syncs with PR #3686 in dotnet/docs (#561) --- .../no-longer-able-to-set-enableviewstatemac-to-false.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/compatibility/no-longer-able-to-set-enableviewstatemac-to-false.md b/Documentation/compatibility/no-longer-able-to-set-enableviewstatemac-to-false.md index b855480..5e9aad4 100644 --- a/Documentation/compatibility/no-longer-able-to-set-enableviewstatemac-to-false.md +++ b/Documentation/compatibility/no-longer-able-to-set-enableviewstatemac-to-false.md @@ -10,13 +10,13 @@ Major Available ### Change Description -ASP.NET no longer allows developers to specify `` or `<@Page EnableViewStateMac="false" %>`. The view state message authentication code (MAC) is now enforced for all requests with embedded view state. Only apps that explicitly set the EnableViewStateMac property to false are affected. +ASP.NET no longer allows developers to specify `` or `<@Page EnableViewStateMac="false" %>`. The view state message authentication code (MAC) is now enforced for all requests with embedded view state. Only apps that explicitly set the EnableViewStateMac property to `false` are affected. - [ ] Quirked - [ ] Build-time break ### Recommended Action -EnableViewStateMac must be assumed to be true, and any resulting MAC errors must be resolved (as explained in [this](https://support.microsoft.com/en-us/kb/2915218) guidance, which contains multiple resolutions depending on the specifics of what is causing MAC errors). +EnableViewStateMac must be assumed to be true, and any resulting MAC errors must be resolved (as explained in [this guidance](https://support.microsoft.com/en-us/kb/2915218), which contains multiple resolutions depending on the specifics of what is causing MAC errors). ### Affected APIs * Not detectable via API analysis