之所以命名ASP.NET会话Cookie名称？ [英] Reason to rename ASP.NET Session Cookie Name?

问题描述

没有任何理由（安全？）为什么有人要的改名的ASP.NET会话Cookie名称或者是ASP.NET的只是一个毫无意义的选择吗？

is there any reason (safety?) why someone should rename the ASP.NET Session Cookie Name or is it just a senseless option of ASP.NET?

推荐答案

如果您在同一台服务器上同一个域下运行多个应用程序，你可能希望有单独的会话cookie的名字为每一个，让他们AREN 'T共享相同的会话状态或更糟的是互相覆盖。

If you have several applications running under the same domain on the same server, you may well want to have seperate session cookie names for each one, so that they aren't sharing the same session state or worse still overwriting each other.

另见href=\"http://msdn.microsoft.com/en-us/library/1d3t3c61.aspx\">窗体身份验证cookie名称的

See also the notes for the Forms Auth cookie name:

指定的HTTP cookie用于身份验证。如果多个应用程序在单个服务器上运行，并且每个应用程序都需要一个唯一的cookie，你必须为每个应用程序的每个Web.config文件中配置cookie的名称。

Specifies the HTTP cookie to use for authentication. If multiple applications are running on a single server and each application requires a unique cookie, you must configure the cookie name in each Web.config file for each application.

这篇关于之所以命名ASP.NET会话Cookie名称？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！