title: AntiForgeryConfig.CookieName inconsistent with HttpContext.Request.Cookies - why?
body: <p>We have an app written in ASP.NET MVC 3, that uses <code>@Html.AntiForgeryToken()</code>.</p>
  
  <p>We want to validate the token in our custom attribute (without a need of specifying the default attribute <code>[ValidateAntiForgeryToken]</code>). This should be pretty straightforward, but I've found an interesting inconsistency.</p>
  
  <ol>
  <li><p>All the code below is running within the following method:</p>
  
  <pre><code>[AttributeUsage(AttributeTargets.Method | AttributeTargets.Class, AllowMultiple = false, Inherited = true)]
  public class ValidateJsonAntiForgeryTokenAttribute : FilterAttribute, IAuthorizationFilter
  {  
      public void OnAuthorization(AuthorizationContext filterContext)
      {
      ...
  </code></pre></li>
  <li><p><code>AntiForgeryConfig.CookieName</code> value is <code>__RequestVerificationToken</code>. That seems to make sense.</p></li>
  <li><p><code>filterContext.HttpContext.Request.Cookies</code> contains 1 cookie - but its name is <code>__RequestVerificationToken_Lw__</code>.</p></li>
  </ol>
  
  <p><strong>Question:</strong> aren't those two supposed to be the same so I can use following snippet to get the cookie?</p>
  
  <pre><code>var cookie = filterContext.HttpContext.Request.Cookies[AntiForgeryConfig.CookieName];
  </code></pre>