奇怪的会话超时问题（需要紧急帮助）。 [英] Strange session timeout problem(urgent help needed).

问题描述

你好，

我正在努力解决一个有点不太了解的会话场景。

我提供基于我的页面的访问权限表单身份验证使用

会话cookie。


我的页面的Som应该连续运行并刷新一次
每小时
。

我在< sessionState部分设置了超时= 61，在我的页面上显示

< meta http-equiv =" refresh" content =" 3600">。

我还在web.config的< forms部分设置了timeout = 120，以确保cookie没有过期

会话已经更新。


但是无论如何我每隔3600秒就得到一次。

有人可以解释一下吗？


非常感谢提前。


JB

Hello,
i''m struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.

Som of my pages are supposed to be running continuously and refreshing once
an hour.
I there set timeout= 61 in <sessionState section and on my page it says
<meta http-equiv="refresh" content="3600">.
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.

But anyway i''m getting the temeout every 3600 seconds.
Can someone explain this?

Many thanks in advance.

JB

推荐答案

其实，很有意义的是，如果你在< sessionState中有
timeout = 61，那么会话

将在大约3600秒内到期。


请记住，超时值以分钟表示。


如果您的会话需要更长的到期时间，

设置timeout = in< sessionState to 120，如果那就是你需要的。


如果你这样做，会话将在7200秒后到期。


请注意，会话到期时间越长，

越多内存消耗，在某些时候，由于没有足够的内存，你可能会因为回收的应用程序而结束，所以你的所有会话都会过期。


您必须进行实验并寻找

配置的会话到期时间和应用程序回收时间之间的权衡。


Juan T. Llibre

ASP.NET MVP
http://asp.net.do/foros/

Foros de ASP.NET en Espa？ol

Ven，y hablemos de ASP.NET ...

======================


" jensen bredal" < JE *********** @ yahoo.dk>在留言中写道

news：uT ************** @ TK2MSFTNGP09.phx.gbl ...

Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState, that the sessions
would expire in approximately 3600 seconds.

Remember that the timeout value is expressed in minutes.

If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that''s what you need.

If you do, the sessions will expire in 7200 seconds.

Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.

You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa?ol
Ven, y hablemos de ASP.NET...
======================

"jensen bredal" <je***********@yahoo.dk> wrote in message
news:uT**************@TK2MSFTNGP09.phx.gbl...

你好，
我正在努力解决一个不太明白的会话场景。
我使用
会话cookie基于表单身份验证提供对我的页面的访问。

Som of我的页面应该每小时持续运行一次。
我在< sessionState部分和我的页面上设置了超时= 61
说
< meta HTTP的当量= QUOT;刷新" content =" 3600">。
我还在web.config的< forms部分设置了timeout = 120，以确保在会话更新之前cookie不会过期。但是无论如何我每隔3600秒就会得到一次。
有人可以解释一下吗？

非常感谢提前。

JB

Hello,
i''m struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.

Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600">.
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.

But anyway i''m getting the temeout every 3600 seconds.
Can someone explain this?

Many thanks in advance.

JB

但是我如何避免我的会话超时仍然保持刷新

时间到1小时（3600秒）？


" Juan T. Llibre" <无*********** @ nowhere.com>在消息中写道

新闻：％2 **************** @ TK2MSFTNGP09.phx.gbl ...

But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?

"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

其实，很有意义的是，如果你在< sessionState中有
timeout = 61，会话
将在大约3600秒内到期。

请记住超时值以分钟表示。

如果您的会话需要更长的到期时间，请将timeout = in< sessionState设置为120，如果这是您需要的。

如果你这样做，会话将在7200秒后到期。

注意会话到期时间越长，内存消耗越多，在某些时候，
由于缺乏足够的内存，你可能会收到回收的应用程序，所有的会话都会过期。

你必须进行实验并寻找交易 - 配置的会话到期时间和应用程序回收时间之间的关闭。

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa？ol
Ven，y hablemos de ASP.NET ...
===================== = jensen bredal" jensen bredal" < JE *********** @ yahoo.dk>在消息中写道
新闻：uT ************** @ TK2MSFTNGP09.phx.gbl ...

Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState, that the sessions
would expire in approximately 3600 seconds.

Remember that the timeout value is expressed in minutes.

If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that''s what you need.

If you do, the sessions will expire in 7200 seconds.

Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.

You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa?ol
Ven, y hablemos de ASP.NET...
======================

"jensen bredal" <je***********@yahoo.dk> wrote in message
news:uT**************@TK2MSFTNGP09.phx.gbl...

你好，
我正在努力解决一个有点不太了解的会话场景。
我使用
会话cookie基于表单身份验证提供对我的页面的访问。

我的页面的索引被认为是每小时一次持续运行并刷新。
我在< sessionState部分和我的页面上设置了超时= 61

< meta http-equiv = "刷新" content =" 3600">。
我还在web.config的< forms部分设置了timeout = 120，以确保在会话更新之前cookie不会过期。但是无论如何我每隔3600秒就会得到一次。
有人可以解释一下吗？

非常感谢提前。

JB

Hello,
i''m struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.

Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600">.
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.

But anyway i''m getting the temeout every 3600 seconds.
Can someone explain this?

Many thanks in advance.

JB

刷新时间并不重要。


如果您的会话超时设置为20分钟，

并且在所有页面中进行元刷新，设置为19分钟，

您可以拥有会话不断更新，没有

需要在120分钟内累积RAM资源。


只要用户打开您网站的页面，会话

将自动延长20分钟。


如果他们关闭了您网站的所有页面，即，如果他们消失了

永久，然后会议woul d在最后一页打开后刷新20分钟

。


实际上不需要有大的会话超时值。



Juan T. Llibre

ASP.NET MVP
http://asp.net.do/foros/

Foros de ASP.NET en Espa？ol

Ven，y hablemos de ASP.NET ...

======================

" jensen bredal" < JE *********** @ yahoo.dk>在留言中写道

news：e％**************** @ TK2MSFTNGP15.phx.gbl ...

The refresh time is immaterial.

If you have your session timeout set to 20 minutes,
and have a meta refresh, in all your pages, set to 19 minutes,
you could have your sessions continually refreshed, without the
need to accumulate RAM resources over 120 minutes.

As long as a user has a page at your site open, the sessions
would be automatically extended for another 20 minutes.

If they close all pages at your site, i.e., if they go away
permanently, then the sessions would expire 20 minutes
after the last page open was refreshed.

There''s really no need to have large session timeout values.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa?ol
Ven, y hablemos de ASP.NET...
======================

"jensen bredal" <je***********@yahoo.dk> wrote in message
news:e%****************@TK2MSFTNGP15.phx.gbl...

但是我如何避免我的会话超时仍然保持刷新时间为1小时（3600秒）？

Juan T. Llibre <无*********** @ nowhere.com>在消息中写道
新闻：％2 **************** @ TK2MSFTNGP09.phx.gbl ...

But then how do i avoid my session to timeout still keeping the refresh
time to 1 hour (3600 seconds)?

"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

实际上，它做了很多感觉，如果你在< sessionState中有
timeout = 61，会话
将在大约3600秒内到期。

请记住，超时值以分钟表示。

如果您的会话需要更长的到期时间，
将timeout = in< sessionState设置为120，如果这就是您需要的。
如果你这样做，会话将在7200秒后到期。

注意会话到期时间越长，内存消耗越多，在某些时候，
由于缺乏足够的内存，你可能最终会使用可回收的应用程序，所有的会话都会过期。

你必须进行实验并寻找一种权衡。配置会话到期时间和应用程序回收时间。

Juan T. Llibre
ASP.NET MVP
< a rel =nofollowhref =http://asp.net.do/foros/target =_ blank> http://asp.net.do/foros/
Foros de ASP.NET en Espa？ol
Ven，y hablemos de ASP.NET ...
====================== />
jensen bredal < JE *********** @ yahoo.dk>在消息中写道
新闻：uT ************** @ TK2MSFTNGP09.phx.gbl ...

Actually, it makes a lot of sense that, if you have
timeout= 61 in <sessionState, that the sessions
would expire in approximately 3600 seconds.

Remember that the timeout value is expressed in minutes.

If you need a higher expiration time for your sessions,
set timeout= in <sessionState to 120, if that''s what you need.

If you do, the sessions will expire in 7200 seconds.

Take note that the larger the session expiration time,
the more memory consumption and that, at some point,
you might wind up with a recycled application due to
lack of sufficient RAM, and all your sessions will expire anyway.

You will have to experiment and look for a trade-off between
configured session expiration time and application recycling time.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa?ol
Ven, y hablemos de ASP.NET...
======================

"jensen bredal" <je***********@yahoo.dk> wrote in message
news:uT**************@TK2MSFTNGP09.phx.gbl...

你好，
我正在努力解决一个有点不太了解的会话场景。
我使用
会话cookie基于表单身份验证提供对我的页面的访问。

我的页面的索引被认为是每小时一次持续运行并刷新。
我在< sessionState部分和我的页面上设置了超时= 61

< meta http-equiv = "刷新" content =" 3600">。
我还在web.config的< forms部分设置了timeout = 120，以确保在会话更新之前cookie不会过期。但是无论如何我每隔3600秒就会得到一次。
有人可以解释一下吗？

非常感谢提前。

JB

Hello,
i''m struggling with a somehow badly understood session scenario.
I provide acces to my pages based on form authentication using
Session cookies.

Som of my pages are supposed to be running continuously and refreshing
once an hour.
I there set timeout= 61 in <sessionState section and on my page it
says
<meta http-equiv="refresh" content="3600">.
I also set timeout=120 in the <forms section of web.config to make sure
the cookie does not expire before the session has been renewed.

But anyway i''m getting the temeout every 3600 seconds.
Can someone explain this?

Many thanks in advance.

JB

这篇关于奇怪的会话超时问题（需要紧急帮助）。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！