title: Using the antiforgery cookie in ASP.NET Core but with a non-default CookieName
body: <p>I'm thinking about changing name of the default antiforgery cookie in ASP.NET Core.</p>
  
  <p>The reason why I would like to change the cookie name is to anonymize the cookie, in my opinion there is no reason why end users should be able to determine the responsibility of this cookie.</p>
  
  <p><a href="https://docs.asp.net/projects/api/en/latest/autoapi/Microsoft/AspNetCore/Antiforgery/AntiforgeryOptions/index.html#prop-Microsoft.AspNetCore.Antiforgery.AntiforgeryOptions.CookieName" rel="noreferrer">Microsoft.AspNetCore.Antiforgery.AntiforgeryOptions.CookieName</a></p>
  
  <ol>
  <li>How do I change the name of the antiforgery cookie? I guess it should be done in the <strong>Startup.cs</strong> file in somehow?</li>
  <li>What possible implications could occur by changing name the default antiforgery cookie?</li>
  <li>How do I use the antiforgery cookie in ASP.NET Core?</li>
  <li>Should different web applications (using same domain) share single antiforgery cookie, or should separate antiforgery cookies be created for each web application?</li>
  </ol>