会话状态丢失 [英] Session state being lost
问题描述
你好，
我有一个以两种配置运行的Web应用程序：
1.在我的本地计算机上运行调试和发布模式
2.在发布模式下共享，托管，机器上
在我的本地机器上，应用程序永远不会丢失其会话
state（这是我管理应用程序登录状态的方式）。
在共享计算机上，会话状态似乎是间歇性地重置
。我看到这表现为一个用户
被踢回登录屏幕还能够b $ b返回返回到上一个受保护的页面，并且仍然可以使用
会话。
我的应用程序在会话中存储一些数据
识别当前登录到应用程序的用户。
我通过执行
跟踪来检测用户何时未登录：
1.检查会话是否是新的
2.检查是否存在登录状态
所以我思考会话在
共享服务器上标记为新，但登录状态对象仍在
会话中。
我对这两种配置的配置是：
会话模式= InProc
Sesion内存= 1 GB（在共享服务器上）
ASP.NET版本= 1.1
共享服务器上看到什么或者什么不是？我使用表格尝试
基于身份验证，但无法使用b $ b来使其适用于两种类型的登录工作
我需要支持。
谢谢
- Jacob Anderson
jw*@beyond-ordinary.com
有一些病毒扫描程序，触摸web.config或其他一些重要的
app文件，并强制应用程序重启和会话丢失。
-
-
德米特里安德列夫。 MCSD.NET
" Jacob Anderson" < jw*@beyond-ordinary.com>在消息中写道
news：03 **************************** @ phx.gbl ... < blockquote class =post_quotes>你好，
我有一个以两种配置运行的Web应用程序：
1.在我的本地机器上以调试和发布模式运行 2.在发布模式下共享，托管，机器上
在我的本地计算机上，应用程序永远不会丢失其会话状态（这是我管理应用程序登录状态的方式） 。
在共享机器上，会话状态似乎是间歇性地重置。我看到这表现为用户被踢回。登录屏幕还能够返回到以前受保护的页面，仍然有会话可用。
我的应用程序在会话中存储一些数据，以识别当前登录到应用程序的用户。我检测用户何时没有登录
以下内容：
1.检查会话是否是新的
2.检查是否存在登录状态
所以我思考会话在
共享服务器上被标记为新，但登录状态对象仍然在
会话中。
我对两种配置类型的配置是：
会话模式= InProc
Sesion内存= 1 GB（在共享服务器上）
ASP.NET版本= 1.1
有谁知道在配置或什么不是？我应该在
共享服务器上看什么？我尝试使用表格。基于身份验证，但无法使它能够正常运行两种类型的登录
我需要支持。
谢谢
- 雅各布安德森
jw*@beyond-ordinary.com
我在共享主机站点遇到类似的问题而且还没有找到解决方案。
在哪里设置会话内存？
" Jacob Anderson" < jw*@beyond-ordinary.com>在消息中写道
news：03 **************************** @ phx.gbl ... < blockquote class =post_quotes>你好，
我有一个以两种配置运行的Web应用程序：
1.在我的本地机器上以调试和发布模式运行 2.在发布模式下共享，托管，机器上
在我的本地计算机上，应用程序永远不会丢失其会话状态（这是我管理应用程序登录状态的方式） 。
在共享机器上，会话状态似乎是间歇性地重置。我看到这表现为用户被踢回。登录屏幕还能够返回到上一个受保护的页面仍然有会话可用。
...剪辑...
会话模式= InProc
Sesion memory = 1 GB（在共享服务器上）
ASP.NET版本= 1.1
将会话放在outofproc服务器中。 Sql server。会话问题与asp.net所有版本都很常见。当你使用sql服务器时它就消失了。
也许ms想强迫人们购买它。
" Jacob Anderson" < jw*@beyond-ordinary.com>在消息中写道
news：03 **************************** @ phx.gbl ... < blockquote class =post_quotes>你好，
我有一个以两种配置运行的Web应用程序：
1.在我的本地机器上以调试和发布模式运行 2.在发布模式下共享，托管，机器上
在我的本地计算机上，应用程序永远不会丢失其会话状态（这是我管理应用程序登录状态的方式） 。
在共享机器上，会话状态似乎是间歇性地重置。我看到这表现为用户被踢回。登录屏幕还能够返回到以前受保护的页面，仍然有会话可用。
我的应用程序在会话中存储一些数据，以识别当前登录到应用程序的用户。我检测用户何时没有登录
以下内容：
1.检查会话是否是新的
2.检查是否存在登录状态
所以我思考会话在
共享服务器上被标记为新，但登录状态对象仍然在
会话中。
我对两种配置类型的配置是：
会话模式= InProc
Sesion内存= 1 GB（在共享服务器上）
ASP.NET版本= 1.1
有谁知道在配置或什么不是？我应该在
共享服务器上看什么？我尝试使用表格。基于身份验证，但无法使它能够正常运行两种类型的登录
我需要支持。
谢谢
- 雅各布安德森
jw*@beyond-ordinary.com
Hello,
I have a web application running in two configurations:
1. On my local machine running in debug and release mode
2. On a shared, hosted, machine in release mode
On my local machine, the app never loses its session
state (which is how I manage the login state for the app).
On the shared machine, the session state seems to be
reset intermittently. I see this manifested as a user
being "kicked back" to the login screen yet being able to
go "back" to the previous protected page and still have
the session available.
My application stores some data in the session to
identify the user that is currently logged into the app.
I detect when the user is not logged in by doing the
following:
1. Check if the session is new or not
2. Check for the existence of the login state
So I "think" the session is being marked as ''new'' on the
shared server, but the login state object is still in the
session.
My configuration on both types of configuration is:
Session mode=InProc
Sesion memory = 1 GB (on the shared server)
ASP.NET version=1.1
Does anyone know what things I should look at on the
shared server in terms of configuration or what-not? I
tried using "forms" based authentication, but could not
ever get it to work properly for the two types of logins
I need to support.
Thanks
-- Jacob Anderson
jw*@beyond-ordinary.com
There some virus scanners, what touch web.config or some other important
app files , and force application restart and session lost.
--
--
Dmitry Andreev. MCSD.NET
"Jacob Anderson" <jw*@beyond-ordinary.com> wrote in message
news:03****************************@phx.gbl...Hello,
I have a web application running in two configurations:
1. On my local machine running in debug and release mode
2. On a shared, hosted, machine in release mode
On my local machine, the app never loses its session
state (which is how I manage the login state for the app).
On the shared machine, the session state seems to be
reset intermittently. I see this manifested as a user
being "kicked back" to the login screen yet being able to
go "back" to the previous protected page and still have
the session available.
My application stores some data in the session to
identify the user that is currently logged into the app.
I detect when the user is not logged in by doing the
following:
1. Check if the session is new or not
2. Check for the existence of the login state
So I "think" the session is being marked as ''new'' on the
shared server, but the login state object is still in the
session.
My configuration on both types of configuration is:
Session mode=InProc
Sesion memory = 1 GB (on the shared server)
ASP.NET version=1.1
Does anyone know what things I should look at on the
shared server in terms of configuration or what-not? I
tried using "forms" based authentication, but could not
ever get it to work properly for the two types of logins
I need to support.
Thanks
-- Jacob Anderson
jw*@beyond-ordinary.com
I am having similar problems at a shared hosting site and have not as yet
found a solution.
Where does one set the Session Memory?
"Jacob Anderson" <jw*@beyond-ordinary.com> wrote in message
news:03****************************@phx.gbl...Hello,
I have a web application running in two configurations:
1. On my local machine running in debug and release mode
2. On a shared, hosted, machine in release mode
On my local machine, the app never loses its session
state (which is how I manage the login state for the app).
On the shared machine, the session state seems to be
reset intermittently. I see this manifested as a user
being "kicked back" to the login screen yet being able to
go "back" to the previous protected page and still have
the session available.
...clipped...
Session mode=InProc
Sesion memory = 1 GB (on the shared server)
ASP.NET version=1.1
Put session in an outofproc server. Sql server. Session problems are very
common with asp.net all versions. It goes away the moment u use sql server.
Maybe ms wants to force people to buy it.
"Jacob Anderson" <jw*@beyond-ordinary.com> wrote in message
news:03****************************@phx.gbl...Hello,
I have a web application running in two configurations:
1. On my local machine running in debug and release mode
2. On a shared, hosted, machine in release mode
On my local machine, the app never loses its session
state (which is how I manage the login state for the app).
On the shared machine, the session state seems to be
reset intermittently. I see this manifested as a user
being "kicked back" to the login screen yet being able to
go "back" to the previous protected page and still have
the session available.
My application stores some data in the session to
identify the user that is currently logged into the app.
I detect when the user is not logged in by doing the
following:
1. Check if the session is new or not
2. Check for the existence of the login state
So I "think" the session is being marked as ''new'' on the
shared server, but the login state object is still in the
session.
My configuration on both types of configuration is:
Session mode=InProc
Sesion memory = 1 GB (on the shared server)
ASP.NET version=1.1
Does anyone know what things I should look at on the
shared server in terms of configuration or what-not? I
tried using "forms" based authentication, but could not
ever get it to work properly for the two types of logins
I need to support.
Thanks
-- Jacob Anderson
jw*@beyond-ordinary.com
这篇关于会话状态丢失的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
