How do I change the session timeout?

[=?ISO-8859-1?Q?G=F6ran_Andersson?=]

re:

I tried it...until your bullheadedness continued insisting that you
were right when you were clearly wrong, wasting everybody's time.

On what have you based your theory that i am "clearly wrong"? Is that
based on the false proof that you presented earlier?

You did the same thing in the floating point thread.

You don't understand reasoned argument, and think that you're right
...because you *think* you're right, without the need for showing any proof,
and without analyzing what others reply to you...which proves you wrong.

I have analysed your "proof" and explained what's wrong with it.

I don't have anything against admitting that I am wrong, at least not
much, but your false proof is clearly not reason enough to do so. I am
not wrong just because you think that I am.

I have news for you : you were *not* right;
not in this thread and not in the floating point thread, where you *also* wasted everybody's time.

You have *not* shown *any* proof that what you argued regarding IIS is right.

You have *not* shown *any* proof that what you
argued regarding the time for sessions to exist is right.

It's true that I haven't presented any proof, but you haven't shown any
valid proof for what you are arguing either. I don't understand why you
make a point of that I haven't shown any proof, when you haven't either.

Otoh, you have great capacity to continue thinking
that you're right when you've been proven to be wrong.

I have yet to see any proof.

What you call "demeaning" is an accurate reflection of the truth.

No, it's not. It's only your opinions that you spread in the form of
insults. What you think does not automatically become truth.

 

[Juan T. Llibre]

re:

It's true that I haven't presented any proof, but you haven't shown any valid proof for what you
are arguing either.

You haven't tested the code I sent, then, nor clicked on the links I've sent, then.

Where's your code and/or proof/support for your argument that :

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

???

I'd like to see you demonstrate that. Why don't you ?
That way, youi'll prove to everybody that *I* am blowing hot air, and not you.

IIS has nothing to do with session length.
Session length is determined by ASP.NET or by any ISAPI application within IIS, like ASP.

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

Where's your code and/or proof/support for your argument that :

!> When the application starts at the same time as the session, as in your test

???

I *showed* you that your argument isn't true.

Look at 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

Where's your code and/or proof/support for your argument that :
!> As they are the same, the test doesn't prove anything at all.

???

They are *not* the same, as proven by the above link.
....and the test I provided *does* prove that your assumptions are mistaken.

....and this is the last comment I'll make.
You're not worth the time or the effort.

It's just that I don't like it when people willingly
post false information, like you have done, insistently.

 

[Steven Cheng[MSFT]]

Hi Dave,

Yes, forms authentication ticket/cookie is separate from the sessionstate
cookie. You need to configure their timeout setting separately.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

 

[=?ISO-8859-1?Q?G=F6ran_Andersson?=]

re:

You haven't tested the code I sent, then, nor clicked on the links I've sent, then.

Where's your code and/or proof/support for your argument that :

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

???

I'd like to see you demonstrate that. Why don't you ?
That way, youi'll prove to everybody that *I* am blowing hot air, and not you.

IIS has nothing to do with session length.
Session length is determined by ASP.NET or by any ISAPI application within IIS, like ASP.

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

Where's your code and/or proof/support for your argument that :

!> When the application starts at the same time as the session, as in your test

???

I *showed* you that your argument isn't true.

Look at 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

Where's your code and/or proof/support for your argument that :
!> As they are the same, the test doesn't prove anything at all.

???

They are *not* the same, as proven by the above link.
...and the test I provided *does* prove that your assumptions are mistaken.

Lol. You really had me going there. Until your last post I really
thought that you were serious, but now I see that you were kidding all
along.

The "proof" is ingenious. The leap from "the application and session
doesn't always start at the same" to "the application and session never
start at the same time" is really amusing. Especially as it totally
contradicts your first test case, where the application and session
*always* start at the same time.

...and this is the last comment I'll make.
You're not worth the time or the effort.

It's just that I don't like it when people willingly
post false information, like you have done, insistently.

 

[Juan T. Llibre]

re:
!> Especially as it totally contradicts your first test case, where the
!> application and session *always* start at the same time.

Do you *always* jump to absurd conclusions,
or do you, simply, like to imagine non-existent scenarios ?

re:

You haven't tested the code I sent, then, nor clicked on the links I've sent, then.

Where's your code and/or proof/support for your argument that :

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

???

I'd like to see you demonstrate that. Why don't you ?
That way, youi'll prove to everybody that *I* am blowing hot air, and not you.

IIS has nothing to do with session length.
Session length is determined by ASP.NET or by any ISAPI application within IIS, like ASP.

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

Where's your code and/or proof/support for your argument that :

!> When the application starts at the same time as the session, as in your test

???

I *showed* you that your argument isn't true.

Look at 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

Where's your code and/or proof/support for your argument that :
!> As they are the same, the test doesn't prove anything at all.

???

They are *not* the same, as proven by the above link.
...and the test I provided *does* prove that your assumptions are mistaken.

Lol. You really had me going there. Until your last post I really thought that you were serious,
but now I see that you were kidding all along.

The "proof" is ingenious. The leap from "the application and session doesn't always start at the
same" to "the application and session never start at the same time" is really amusing. Especially
as it totally contradicts your first test case, where the application and session *always* start
at the same time.