hi im trying to make a cookie behave like a session so every time i load or reload the page it gives him this line:
Response.Cookies("name").Expires = Now() + 0.015
but its not working..
if i load the page at 10:00 the cookie expires at 10:20
even though i reload the page at 10:10
what can i do? or those a cookie expires can only be set once?
Is it possible to make a cookie NEVER expire? or not?
View Replies View RelatedI've created an admin side for my ASP site and I use session vars to provide
page security.
Just as a bit of advice, I want to know if I should expire each admin page
so that others can't bring them up. I know the session var check will
bounce them back to the login page, but I'd rather they didn't even see this
page if they aren't authorised.
I want to expire a cookie collection in my asp page and I gave it like this;
Response.Cookies("whereq").Expires = Now()
and this "whereq" collection has 50 keys. The problem is my cookie didn't expire from the above code. I hope there should be a way to do so without writing 50 expire lines.
How does the expire date work setting it server side with asp.
I know with javascript setting it client side it will be set to the clients
local time, and therefore expire when the clients local time reaches the set
expire-time.
But if it is an expire time set on my server in California, and the cookie
is put on a computer that is running on London Time, and the expire time is
set at the server as 20 minutes from now, the London computer will think
that the cookie has expired 7 hours and 40 minutes ago, right?
How does this actually work? Is it proper to just set my expire time as:
dtmExp = DateAdd("n", 20, Now())
Response.Cookies("MyCookie").Expires = dtmExp
understand that when one closes the browser, the session gets killed in ASP,
i encountered a scenario, where even after the browser was closed, the session was active, let me explain, i have written a code to check if the session variable contains the loginname then i am allowing access to a certain asp page to the user.
the code worked. thereafter i closed the browser, opened the browser again and accessed the same url, surprisingly it allowed access to the page and did not ask me for the login name, clearing the cache also did not help.
Further, I need to update some table as well when the user closes his browser window (an update query to set the flag to 0 for tracking user status). How can I do this. A sample code will be highly appreciated.!
Lastly, when the user clicks the logoff button, he successfully logout , but he can come back with the back button on the browser. Is there a way to prevent this,that is, once the user logout and tries to come back, he SHOULD NOT be allowed to do so rather he should be redirected to a page where he can login again.
Session expiring immediately. what could be the reason ?
View Replies View Relatedif user clicked the Sign Out button, the session abandon and the login page displays. If the user clicks the browser Back button, it won't show the previous page. It shows only the login page. How does is work?
View Replies View Relatedi have 2 application variables called totalAdminLoggedIn and totalUserLoggedIn
when ever an admin login, I increment the totalAdminLoggedIn value by one
and when a normal user logg in, the totalUserLoggedIn value will be incremented by one.
how can i change the values when the session expire ? i can reduce the value manually when they logoff like:
if session("userCategory")="admin" then
Application("totalAdminLoggedIn")=Application("totalAdminLoggedIN")-1
elseif session("userCategory")="user" then
Application("totalUserLoggedIn")=Application("totalUserLoggedIn")-1
end if
session.contents.remove "userCategory"
but what if the session expires automatically or if they close the window suddenly?
ie. i want to do something like below? Code:
i want to increase my session time so that it does not expire till the user closes the site.
i have written in global.asa file the following code:
<SCRIPT LANGUAGE="VBScript" RUNAT="Server">
Sub Session_OnStart
Session.Timeout = -1
End Sub
</script>
but it doesnt work and my sesion still expires.
I want to know what's the differences between session cookie and regular cookie.
In ASP, when we create cookie, we do the following to identify an user:
Response.Cookies("name") = value
Is this regular cookie? How about session cookie? and when to use which?
how to make the session timeout. and where should i put the session timeout.
View Replies View RelatedI have a site that I'm trying to migrate to ASP.NET from ASP, and the
foremost stumbling block I'm hitting is session state between the ASP
and ASP.NET applications. In order to access this information, I'm
doing a HttpWebRequest from the ASP.NET side into an .asp page,
passing the session name on the get in order to request it from the
ASP side and write it back to the response stream, giving ASP.NET
access to it. Of course I change sessions each time I make the call
from the ASP.NET side.
Soooooo, I'm thinking to myself, "Self, shouldn't you be able to fake
out the server by getting the session cookie from the initial usage of
the asp, pass that data to the ASP.NET, and use that to send a request
back the ASP side under the appropriate session?"
From a real high level, I enter the site via a .asp page. This page
in turn calls .aspx page from within a frame ......
Can anyone tell me the difference between Session and Cookie? Does Application Object and Session works the same way?
How do we know when to use Session and cookie?
I am not asp specialist and i was wondering what to choose - session or a cookie.
the idea is to make something like a shop but without the function "remember me" ... more like "in memory" cookies. so apparently i will have to use a session or a "in memory" cookie but which one is better. as to my knowledge the session does not differ dramaticaly from the cookie because it uses because as u know it is based on cookies. however why should i use session instead of cookies if the result will be exact the same i.e. if browser does not support cookies the whole thing won't work out?
How would the server know the user has viewed a new post in a discussion forum? All the posts that started today will display in bold. Once I view the post, and the post will display in regular text?
View Replies View RelatedDoes anybody knows how to change it?
Instead of ASPSESSIONIDQARCQQSC I want to change to "ASPSERVER1" for example...
I'm seeing a problem with IE running on OS-X. When the user logs in to the
website (ASP/IIS5), a Session is established properly, but somewhere along
the line, a new Session is created and abandoned. At that point, the user
must log in again due to the code logic (their Session is "gone" and they're
then invalid). The original Session's On_End event never fires (or perhaps
it doesn't until the timeout which is 40 minutes).
I am monitoring the Session_OnStart and Session_OnEnd events with debug
code.
This problem only exists for this one user and the only difference between
her and the other users is that she's running IE on OS-X. IE on OS-9 works
fine as does IE on Windows.
IE version 5.2.1 (4717)
OS-X version 10.2.4
First, I like to know if I can specify how long a session variable could expire?
I am having problem with user logged in period when using session variable.
When I logged in and go away from keyboard for like 10mins. By then I have to login again in order to post or any website features that requires login.
I have not yet create a cookie for the user when they are login.
What is the proper way of doing it?
The session_onstart event will fire for every pull BECAUSE no SESSIONID cookie is ever created and the server has to assume that every HTTP REQUEST frame is a new session. The response object is actually just setting a header, of course.
Every redirect is sending a header to the browser equivalent to a "meta refresh" and that once again triggers the session_onstart.
There are two cookie types:
1) session cookie.
2) persistent cookie is the same as tracking cookie?
Is that correct?
For windows machine, the files in C:Documents and SettingsAdministratorCookies
are all persistent cookie, it doesn't have session cookie?
How session cookies are stored? Session cookie should expire once the browser is closed.
If I start a session on our web app then close all browsers, I expect that
the session cookie would be deleted and that the session itself would exist
until it expired. I then start a new instance of the browser expecting to
get a new session id and a new session, but instead I reconnect to the
unexpired session. Does anyone know why the session cookie is persisting
despite the closure of all the IE windows?
I'm not exactly hot on asp, but I have managed to create a members area / pages on a site that requires the usual login etc through username and passwords.
The problem that I'm having is that people are being logged out and forced to log back in etc.
Here's the code for the log-in form on the site: ....
how I could store the referrer id in this URL http://www.widget.co.uk?referrer=1234 into a session cookie. I've been given this code by someone else but my knowledge of ASP is virutally non-existent and they need this feature in the site as soon as possible.
<%dim vntRef
if request.querystring("referrer") <> "" then
vntRef = request.querystring("referrer")
session("svRef") = vntRef
end if
if session("svRef") = "" then
session("svRef") = vntRef
end if
%>
where this code goes and how I reference it(if I need to) that would be fantastic. Basically I wasn't told about this until after the site went live and they're now telling me to get it done quick smart so the quicker the better.
I need to set a session cookie with an array(100+) and ad values to the array every time the user choses to ad something (to the array while she/he is navigating the site) and write the content of the array on the page after each addition to the array! So, basically:
1- Set session cookie with array. 2- ad values to the array and write out the whole array after each addition automatically, otherwise just write "no choices" or smth. Can anyone show how to do this codes in ASP briefly?
I'm writing an application to authenticate a user using a challenge
response mechanism. The client and server components of the
application talk over HTTP.
I would like to use an ASP session object to hold a random number on
the server. The code to store the number is written as part of a VB
web class.
When I read the http header returned from my server, I can't see the
session cookie. Why is this? If I create a normal cookie as part of
my web class, it is returned correctly within the header.
I am using HttpQueryInfo the read the header as follows:
blnReturn = CBool(HttpQueryInfo(hOpenRequest, HTTP_QUERY_RAW_HEADERS,
ByVal strBuffer, Len(strBuffer), 0))
I want to know if user disable cookie, will the session still working? Actually I remember we could disable cookie in IE before (not sure what version, but I couldn't see
the option anymore. Now I am using IE6.
I am having a problem tracking down what I believe to be a problem with
the way cookies are being used on our website application.
When user log onto the application, an in-memory (per-session) cookie
is created to hold the session key for the user. This unique key is
assigned as part of the business layer logon process, and never changes
while the user is logged on. The call to the business component returns
this unique key if the logon was successful, and the cookie is set up
as follows:
Response.Cookies("SessionKey").Path = "/"
Response.Cookies("SessionKey") = strSessionKey
Nowhere is the cookie assigned an .expires value.
Once a user has completed this logon process, they must then click past
an intermediate agreement page before actually having access to the main
application. When this intermediate page is submitted, it accesses the
cookie, extracts the session identifier and writes the value to a
database table.
The code to achieve this looks something like:
strSessionKey = Request.Cookies("SessionKey")
Dim objInstance
Set objInstance = Server.CreateObject("SomeComponent.SomeClass")
objInstance.StoreIdentifier strSessionKey
Set objInstance= nothing
The whole process works fine until I try to do the second stage (the
intermediate agreement) with two separate IE sessions (there are 2
separate IEXPLORER.EXE entries in task manager) very quickly.
I can go through the whole process fine, and then while leaving the
application open, I can start again with a new IE window and complete
the process again. In each case the correct identifier is stored in the
database for each separate session.
If I get to the second stage of the logon process with 2 separate IE
sessions, and submit both agreement pages at the same time (or as close
together as I can), then they both write the same unique session
identifier to the database, as if they are accessing the same cookie!
The session identifier used is the one from the first agreement page I
submit. This definitely only happens if I do this at the same time.
Wait a few seconds between the submissions and all is well.
Has anyone come across something like this before and can advise on a
possible reason?
is it possible to delete a cookie? without ending the session?
View Replies View RelatedI want to set the asp session id path property. How can I do that?
I mean, asp session id is stored in a cookie and like any other cookie it should have properties (or attributes), how can I control it?
We are working on an old asp project and we noticed that some users get
kicked out of the session right after they log in.
I investigated the issue and I found the cause:
1- The user login successfuly.
2- He gets redirected to the menu screen. that's when I set some
cookies to cookie("cookie name").expires = Now. that when the session
starts to disapear, once the user tries to access other pages (or even
refresh), the ASPSESSIONID cookie disapears.
I did some debugging on the http_cookie collection and looks like the
ASPSESSION disapears once I set the cookie expiration, although I set
the expiration for cookies unrelated to the ASPSESSIONID.
Here is the tricky thing, it works on 90% of the machines, and it
doesn't on other machines, it's also random, so some users who had the
problem, are now able to work on the system and the problem disapeard.
Have you guys ever had this problem, or do you know if it is related to
IE batches or service packs?
When I use a host file entry to point to the host header of the site
that I have created on a Win2k server running IIS5, a cookie is not
created to hold the session id. The result is that Session_OnStart is
run every time a page is requested.
If I set up a DNS entry on the DNS server it all works fine.
I never noticed this problem before we put in Active Directory so it
may have something to do with that.
I have set "allow per session cookies" to promt(under Custom Secrity
settings in IE) to see if this is being attempted and it is not. So
the browser is not even trying to create the session cookie when using
the host file.
I am making a news letter application for my company. The idea is that if the cookie (fictional name Frankie ) don't exist a newsletter is being sent to all subscribers.
View Replies View Related