Re: How do I change the session timeout?

re:
When the application starts at the same time as the session, as in your test

You know diddly-sh*t, clearly.

Click on this link and see that the Application's
start time occurs earlier than the Session's start time

http://asp.net.do/test/sessionID.aspx

re:
As they are the same, the test doesn't prove anything at all.

They are *not* the same, as proven by the above link.

Now, backtrack a bit to what you wrote...and are ignoring :

!> "The IIS only clears out old sessions once a minute, so the sessions will live up to two
minutes."

Exactly, how do you prove that to be true ?

re:
!> Ok, it might not IIS itself, but ASP.NET, that runs in the IIS environment, that does that.
!> Does it make any difference, really?

It *does* make a difference because other http applications, like ASP,
will set their own timeouts, and IIS *still* won't have anything to do with that.

I agree with Mark.
You are a hopeless case when it comes to admitting your mistakes.

It's sad, considering that you think you're a bright young man, except that
your bullheadedness when it comes to admitting you're wrong about
something won't let you get to be a smart old man.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Göran Andersson" <guffa@xxxxxxxxx> wrote in message news:OaKonj8cHHA.4260@xxxxxxxxxxxxxxxxxxxxxxx
Juan T. Llibre wrote:
re:
Yes, it is.

Jeez, you *are* argumentative aren't you ?

Perhaps. And you are trying to imply that you aren't?

...even when you're -evidently- mistaken.

Well, the evidence for that is still to be presented.

I supplied you with sample code which proves that what you stated is not true.
Prove that my sample code isn't valid by supplying us with code which proves you're right.

No, you haven't. The sample code is valid, but it doesn't at all prove what you now claim that it
does.

re:
!> What you are demonstrating is that the timeout is occuring at one minute
!> intervals from the starting time of the application, not that it is running every second.

You should re-read my sample code.

I have re-read your sample code, and even tried it for myself. It works as expected, but it still
has no bearing on this discussion. The only thing that contradicts what I have said, is the
conclusions that you mistakenly have drawn from the result.

What I demonstrated is that the *session*, not the application, started at a certain time,
and that one minute and 1 second after the session started, if the timeout is set to 1 minute,
the timeout will occur, and will not live for up to 2 minutes, like you -mistakenly- posted.

When the application starts at the same time as the session, as in your test, it doesn't prove
that the timeout interval is based on the starting time of the session rather than the
application. As they are the same, the test doesn't prove anything at all.

Here's what you wrote :

"The IIS only clears out old sessions once a minute, so the sessions will live up to two
minutes."

First of all, IIS has nothing to do with ASP.NET session timeouts.
IIS doesn't "clear out" anything regarding ASP.NET sessions.

Ok, it might not IIS itself, but ASP.NET, that runs in the IIS environment, that does that. Does
it make any difference, really? Is that what you are so upset about?

Secondly, the sessions will *not* live "up to two minutes".
They will timeout on the first second after the 1st minute expires.

It would be simpler to admit that you're mistaken...on both counts.
We all make mistakes...and this time you made one.



Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Göran Andersson" <guffa@xxxxxxxxx> wrote in message
news:ecvsJs5cHHA.4172@xxxxxxxxxxxxxxxxxxxxxxx
Juan T. Llibre wrote:
re:
The IIS only clears out old sessions once a minute, so the sessions will live up to two
minutes.
Have you tested that ?
Yes, I have.

That is not true.
Yes, it is.

IIS has nothing to do with session length.
Session length is determined by ASP.NET.

And, invariably, if you set the timeout to 1 minute,
at one minute and 1 second after that time, a new session will start.

See my just-sent reply to Steven Cheng and test it yourself.
Yes, if you start a web application by requesting a page from it, you will naturally also start
the mechanism for timing out the pages at the exact same time.

What you are demonstrating is that the timeout is occuring at one minute intervals from the
starting time of the application, not that it is running every second.

--
Göran Andersson
_____
http://www.guffa.com




--
Göran Andersson
_____
http://www.guffa.com




.

Relevant Pages

  • Re: Application Pool timouts.
    ... a) From what i understand, the application pool timeout is the timeout for ... an idle session which is created by a browser. ... is idle for 20 minutes or longer the problems occur. ... Application Pool's w3wp.exe process to be shutdown by IIS when no requests ...
    (microsoft.public.inetserver.iis.security)
  • Re: How do I change the session timeout?
    ... Prove that my sample code isn't valid by supplying us with code which proves you're right. ... What you are demonstrating is that the timeout is occuring at one minute ... What I demonstrated is that the *session*, not the application, started at a certain time, ... IIS has nothing to do with ASP.NET session timeouts. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: extending sessions
    ... timeout is set in IIS, ... Well, the users need to fill in questionnaires, and quite often they click ... And thought of doing this with session, so someone can't just type all the ... If it is ASP.NET site in question, IIS session setting has no impact as ...
    (microsoft.public.dotnet.framework.aspnet.buildingcontrols)
  • Re: How do I change the session timeout?
    ... Prove that my sample code isn't valid by supplying us with code which proves you're right. ... What you are demonstrating is that the timeout is occuring at one minute ... When the application starts at the same time as the session, as in your test, it doesn't prove that the timeout interval is based on the starting time of the session rather than the application. ... IIS has nothing to do with ASP.NET session timeouts. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Session Timeout in IIS & WSS
    ... Are you trying to timeout their connections or their sessions? ... trying to just force authentication again, you simply need to lower the ... these tabs (not in front of a machine with IIS 5 on it) should have the ... default session value. ...
    (microsoft.public.inetserver.iis.security)
Quantcast