Ensuring deleted cookies are recognized by the browser by ensuring the MaxAge within CookieOptions is set to null. (#55169)

* Explicitly appending the MaxAge as null at the end of the delete method to ensure deletion within the browser

* Ensuring the IsEssential property of CookieOptions is carried

* syntax error.

* Simplifying the change to just override MaxAge and Expires when appending

* Adding insightful comment to ResponseCookies.cs

* Ammending the methods DeleteCookie() and DeleteChunks() to ensure MaxAge of cookieOptions is set to null upon deletion

Author: MattyLeslie

src/Http/Http/src/Internal/ResponseCookies.cs

@@ -163,6 +163,7 @@ public void Delete(string key, CookieOptions options)
         Append(key, string.Empty, new CookieOptions(options)
         {
             Expires = DateTimeOffset.UnixEpoch,
+            MaxAge = null, // Some browsers require this (https://github.com/dotnet/aspnetcore/issues/52159)
         });
     }
 

src/Shared/ChunkingCookieManager/ChunkingCookieManager.cs

@@ -304,6 +304,7 @@ public void DeleteCookie(HttpContext context, string key, CookieOptions options)
         responseCookies.Append(keyValuePairs, new CookieOptions(options)
         {
             Expires = DateTimeOffset.UnixEpoch,
+            MaxAge = null, // Some browsers require this (https://github.com/dotnet/aspnetcore/issues/52159)
         });
     }
 
@@ -331,6 +332,7 @@ private static void DeleteChunks(HttpContext context, IRequestCookieCollection r
             context.Response.Cookies.Append(keyValuePairs.ToArray(), new CookieOptions(options)
             {
                 Expires = DateTimeOffset.UnixEpoch,
+                MaxAge = null, // Some browsers require this (https://github.com/dotnet/aspnetcore/issues/52159)
             });
         }
     }