blocks|key|2995289|text|回答你最初的问题:会话与一个放在cookie中的id相关联。此id是使用一些随机数加密例程生成的。不能保证它是唯一的，但它在会话的生命周期中被复制的可能性很小。即使您的会话运行了整个工作日。一个真正受欢迎的网站可能需要数年时间才能生成一个重复的密钥(没有统计数据或事实来支持)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995290|话虽如此，看起来你的问题并不是会话值的混淆。我要开始考虑的第一件事是连接池。默认情况下，ADO池连接，但如果您使用不在池中的用户名/密码请求连接，它将为您提供一个新连接。提示如果您的站点非常大，将来可能会成为性能瓶颈。自从我使用SQL+Server以来，已经有一段时间了，在Oracle中，可以进行一个调用来切换用户的身份。如果在SQL+Server中没有类似的东西，我会很惊讶。您可以尝试使用通用用户名/密码连接到数据库，然后在返回到其余代码的连接之前执行身份切换调用。|2995291|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

To answer your original question: Sessions are keyed to an id that is placed in a cookie. This id is generated using some random number crypto routines. It is not guaranteed to be unique but it is highly unlikely that it will ever be duplicated in the span of the life of a session. Even if your sessions run for full work days. It would probably take years for a really popular site to even generate a duplicate key (No stats or facts to back that up).

Having said all that it doesn't appear that your problem is with session values getting mixed up. The first thing that I would start to look at is connection pooling. ADO pools connections by default but if you request a connection with a username/password that is not in the pool it should give you a new connection. Hint that may be a performance bottleneck in the future if your site is very large. It has been a while since I worked with SQL Server, in Oracle there is a call that can be made to switch the identity of the user. I would be surprised if there was no equivalent in SQL Server. You might try connecting to your DB with a generic username/password and then executing that identity switch call before you hand back the connection to the rest of your code.

blocks|key|3839284|text|这取决于您的会话提供商，如果您以不再唯一的方式覆盖了会话密钥生成，则多个用户可能正在访问同一会话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3839285|你看到了什么行为？你确定你正在讨论的变量中没有静态因素吗？|3839286|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It depends on your session provider, if you have overriden the session key generation in a way that is no longer unique, then multiple users may be accessing the same session. 

What behavior are you seeing? And are you sure there's no static in play with the variables you are talking about?

blocks|key|2994755|text|当一切皆有可能时。。。。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994756|否，除非您将会话状态存储在sql+server或其他进程外存储中，然后对其进行处理。。。|2994757|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

while anything is possible. . . .

No, unless you are storing session state in sql server or some other out of process storage and then messing with it. . .

blocks|key|2994921|text|会话被绑定到用户cookie，在正常情况下这种混乱的机会是非常不可能的，但是如果使用分布式会话状态可能会有问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994922|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The session is bound to a user cookie, the chances of that messing up in a normal scenario is very unlikely, however there could be issues if using distributed session state.

blocks|key|3839419|text|这不可能。会话被绑定到创建者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3839420|你是想搞混，还是你有一个看起来像搞混了的案例？|3839421|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It's not possible. Sessions are tied to the creator.

Do you want to mix up, or do you have a case when it looks like mixed up?

blocks|key|2995049|text|更多信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995050|我有一个应用程序，它从登录页面获取用户in+/密码，并将其存储在一个会话变量中。我将它插入到我的连接字符串中，以便调用SQL+Server。|2995051|当一个表被更新时，我们在数据库中使用'system_user‘来识别’最后更新者‘用户。我们看到一些奇怪的行为，我们期望列出的用户是不正确的，并且它显示的是其他人。|2995052|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

More information:

I've got an app that takes the userid/password from the login page and stores it in a session variable. I plop it into my connection string for making calls to SQL Server. 

When a table gets updated, we're using 'system_user' in the database to identify the 'last updated by' user. We're seeing some odd behavior in which the user we're expecting to be listed is incorrect, and it's showing someone else.

blocks|key|2995135|text|您能否打开调试器，查看是否确实在该连接字符串上传递了正确的值？它将帮助您快速确定问题在哪一方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995136|还要确保没有任何连接代码具有连接或用户的静态属性，否则在更新触发之前，某个用户可能会将其连接替换为最新用户的连接。|2995137|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Can you pop in the debugger and see if the correct value is indeed being passed on that connection string? It would quickly help you idenfity which side the problem is on. 

Also make sure that none of the connection code has static properties for connection or user, or one user may have their connection replaced with that of the most recent user before the update fires off.

blocks|key|753915|text|我的猜测是，您正在重用类上的静态字段来保存连接字符串。这些静态字段会在多个IIS请求中重复使用，因此您可能只会在“上次更新者”中看到最近登录的用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|753916|顺便说一句，除非你有一个很好的理由这样做，否则你不应该像这样连接到数据库。您正在阻止自己使用连接池，这将损害高负载下的性能。|753917|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My guess is that you're re-using a static field on a class to hold the connection string. Those static fields are re-used across multiple IIS requests so you're probably only ever seeing the most recently logged in user in the 'last updated by'.

BTW, unless you have a REALLY good reason for doing so then you shouldn't be connecting to the DB like this. You're preventing yourself from using connection pooling which is going to hurt performance under high loads.

Is it possible for ASP.NET to mix up which user is associated with which session variable on the server? Are session variables immutably tied to the original user that created them across time, space &amp; dimension?

session variable mixup in ASP.NET?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

ASP.NET有可能混淆哪个用户与服务器上的哪个会话变量相关联吗？会话变量是否与创建它们的原始用户跨越时间、空间和维度不可变地捆绑在一起？

问会话变量在ASP.NET中的混用？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会话变量在ASP.NET中的混用？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会话变量在ASP.NET中的混用？
EN