Destroying a Session

[le0]

Hello Guys,

I have this problem on my page. Im doing my "Logoff" portion, everytime I
click "Logoff" then click the Back button in my browser the previous page
still appears.

Heres my code
<%
If Request.QuerySt ring("login")= "logout" Then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon
Response.Redire ct("../../global/common/login/login.asp?login =logoff")
Else

End If
%>

but I think this is not working or there is something wrong with my code
Hope you can help me with this..

Thaks,
Leo

[Janette]

Hi Leo,

The reason the previous page probably displays, is when you click back it
uses the previous URL which would have had login=login in the URL, it is
only the page after logoff that has login=logoff. You would be far better
checking for the existance of the session, or the existance of a particular
session variable having a value instead of setting and checking the
querystring. Else, people may just add login=login to their URL, to bypass
logging in. So for example, when you logon, you might create a session
variable called user and populate it with the username of the person who
just successfully logged on. Then in each page inside the app check for a
value in the user session variable, as it will only have a value if a user
is logged on.

<%
If Session("user") = "" then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Else

End If
%>

Hope this helps.
Janette

"le0" <le*********@gm ail.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

Hello Guys,

I have this problem on my page. Im doing my "Logoff" portion, everytime I
click "Logoff" then click the Back button in my browser the previous page
still appears.

Heres my code
<%
If Request.QuerySt ring("login")= "logout" Then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Response.Redire ct("../../global/common/login/login.asp?login =logoff")
Else

End If
%>

but I think this is not working or there is something wrong with my code
Hope you can help me with this..

Thaks,
Leo

[Stuart Palmer]

If you are using the back button, what you are actually doing is viewing the
same cached file you saw before. A route around this would be to force the
previous page not to cache, I think this would solve your problem.

Stu

--

"le0" <le*********@gm ail.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

Hello Guys,

I have this problem on my page. Im doing my "Logoff" portion, everytime I
click "Logoff" then click the Back button in my browser the previous page
still appears.

Heres my code
<%
If Request.QuerySt ring("login")= "logout" Then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Response.Redire ct("../../global/common/login/login.asp?login =logoff")
Else

End If
%>

but I think this is not working or there is something wrong with my code
Hope you can help me with this..

Thaks,
Leo

[le0]

Hi Janette =)

You are absolutely right, but my page has the include file like this

<%
If Len(Session("Ac cessType")) = 0 Then
Dim sUrlExpire
sUrlExpire =
"../../global/common/login/login.asp?login =expired&sysid= " & strSysPath
%>

<script language=javasc ript>
top.location.hr ef = "<%=sUrlExpire% >"
</script>

<%
Response.End
End If
%>

it checks the accesstype of the user before logging in to the page, and Im
expecting that when I use this code
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon
the sessions will automatically destroyed even if i click the back button =(

Please helppp..

"Janette" <ni**@community .nospamwrote in message
news:ON******** ******@TK2MSFTN GP04.phx.gbl...

Hi Leo,

The reason the previous page probably displays, is when you click back it
uses the previous URL which would have had login=login in the URL, it is
only the page after logoff that has login=logoff. You would be far better
checking for the existance of the session, or the existance of a
particular session variable having a value instead of setting and checking
the querystring. Else, people may just add login=login to their URL, to
bypass logging in. So for example, when you logon, you might create a
session variable called user and populate it with the username of the
person who just successfully logged on. Then in each page inside the app
check for a value in the user session variable, as it will only have a
value if a user is logged on.

<%
If Session("user") = "" then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Else

End If
%>

Hope this helps.
Janette

"le0" <le*********@gm ail.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

>Hello Guys,

I have this problem on my page. Im doing my "Logoff" portion, everytime I
click "Logoff" then click the Back button in my browser the previous
page still appears.

Heres my code
<%
If Request.QuerySt ring("login")= "logout" Then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Response.Redir ect("../../global/common/login/login.asp?login =logoff")
Else

End If
%>

but I think this is not working or there is something wrong with my code
Hope you can help me with this..

Thaks,
Leo

[le0]

Hey Stu,

What dou you mean route around? Can you give me an example =(

=(
Leo

"Stuart Palmer" <tr**********@y oucant.comwrote in message
news:%8******** ***********@new sfe6-gui.ntli.net...

If you are using the back button, what you are actually doing is viewing
the same cached file you saw before. A route around this would be to force
the previous page not to cache, I think this would solve your problem.

Stu

--

"le0" <le*********@gm ail.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

>Hello Guys,

I have this problem on my page. Im doing my "Logoff" portion, everytime I
click "Logoff" then click the Back button in my browser the previous
page still appears.

Heres my code
<%
If Request.QuerySt ring("login")= "logout" Then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Response.Redir ect("../../global/common/login/login.asp?login =logoff")
Else

End If
%>

but I think this is not working or there is something wrong with my code
Hope you can help me with this..

Thaks,
Leo

[Mike Brind]

http://www.aspfaq.com/show.asp?id=2022

--
Mike Brind
le0 wrote:

Hey Stu,

What dou you mean route around? Can you give me an example =(

=(
Leo

"Stuart Palmer" <tr**********@y oucant.comwrote in message
news:%8******** ***********@new sfe6-gui.ntli.net...

If you are using the back button, what you are actually doing is viewing
the same cached file you saw before. A route around this would be to force
the previous page not to cache, I think this would solve your problem.

Stu

--

"le0" <le*********@gm ail.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

Hello Guys,

I have this problem on my page. Im doing my "Logoff" portion, everytime I
click "Logoff" then click the Back button in my browser the previous
page still appears.

Heres my code
<%
If Request.QuerySt ring("login")= "logout" Then
Application.Con tents.RemoveAll ()
Session.Content s.RemoveAll()
Session.Abandon

Response.Redire ct("../../global/common/login/login.asp?login =logoff")
Else

End If
%>

but I think this is not working or there is something wrong with my code
Hope you can help me with this..

Thaks,
Leo

[Dave Anderson]

le0 wrote:

I have this problem on my page. Im doing my "Logoff" portion,
everytime I click "Logoff" then click the Back button in my
browser the previous page still appears.

That is the proper behavior, according to the HTTP specification. The
History belongs to the browser, not to you:

"User agents often have history mechanisms, such as "Back"
buttons and history lists, which can be used to redisplay
an entity retrieved earlier in a session. By default, the
Expires field does not apply to history mechanisms. If the
entity is still in storage, a history mechanism should
display it even if the entity has expired, unless the user
has specifically configured the agent to refresh expired
history documents."

http://www.w3.org/Protocols/HTTP/1.1/spec.html
--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

[Dave Anderson]

I wrote:

That is the proper behavior, according to the HTTP specification.
The History belongs to the browser, not to you:

"User agents often have history mechanisms, such as "Back"
buttons and history lists, which can be used to redisplay
an entity retrieved earlier in a session. By default, the
Expires field does not apply to history mechanisms. If the
entity is still in storage, a history mechanism should
display it even if the entity has expired, unless the user
has specifically configured the agent to refresh expired
history documents."

http://www.w3.org/Protocols/HTTP/1.1/spec.html

In addition,

"History mechanisms and caches are different. In particular
history mechanisms SHOULD NOT try to show a semantically
transparent view of the current state of a resource. Rather,
a history mechanism is meant to show exactly what the user
saw at the time when the resource was retrieved.

By default, an expiration time does not apply to history
mechanisms. If the entity is still in storage, a history
mechanism SHOULD display it even if the entity has expired,
unless the user has specifically configured the agent to
refresh expired history documents."

http://www.w3.org/Protocols/rfc2616/....html#sec13.13

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.