Is it possible to use session in web farm? Some say just use cookies because
session does not work in web farm. But others say something about persist
into SQL Sever, if this is true please tell me more about this approach.
I will soon be undergoing a project where I will be migrating four to five web applications, developed in classic ASP, from a single Windows Server 2000 to a web farm that will utilize two, Windows 2003 Servers.
All of the applications utilize user/session management and I know that ASP's built-in session management cannot be carried across multiple servers.
I've been researching products available for purchase out there on the web, which allows you to include new code, which overrides ASP's built-in session management, by using a database to store sessions.
They all advertise that their solutions simply require just one line of code to be added to each ASP pages that uses Sessions, without any other changes to the existing ASP code.
Can someone who has done something similar advise on their experience? Is this really as easy as they are advertising, or are there other issues to take into consideration? Code:
i have a problem with a web farm. an application asp net 1.1 that works in different servers.doesnt works in the web farm (4 servers balanced). The error it says is "System.Web.HttpCompileException: External component has thrown an exception" basically is a page that its requested in one server and served by other server and are different version of the application .. the technichal staff says its applied the same version in the four servers and i can believe them.
Im using classic ASP (3.0) and I have a web farm with 2 webservers (webserver A and webserver B, both windows server 2003). I do not want to store any client specific information on the webserver (therefore do not intend to use the session object- as you cannot gaurantee which server the user will go to). I want to store a small value (e.g. a Y/N value or an Id) on the client machine for the duration of their browsing session, hence I want to use a non persistent cookie (in client memory) not a persistent cookie that will be written to disk as a file.
Q. Therefore if I create a non persistent cookie (i.e. it resides in the client browsers memory) and set this when the user was on webserver A, can I read the value server side on subsequent requests even if the user is redirected back to webserver B? As the webservers are part of the same domain name Im assuming I can..?
Q. Using non persistent cookies (in client in memory) im assuming the session Id that gets created by IIS has no use, as I am using client side storage, hence it is worth disabling this on the webserver for performance reasons?
Q. Is there a way, when using non persistent cookies that the client user can see the values of this cookie client side, are their any downloadable tools for example they can run?
Im aware of the issues with size of using cookies and users can disable them, my question is more related to using them in a web farm. Im also not intended in the short term to upgrade to asp.net as Im aware there are alternatives for state storage in this. I hope someone can clarify these points for me. Note: I see many articles talking about cookies but none relating to web farms and cookies, those that do talk solely about the session object (Server side), none really go further to talk about (non persistent / persistent cookie usage with web farms client side.
I 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 ......
I want to create an administration page which lists all the current users who are on the site at the moment.
I know coldfusion has this feature built in using the SessionTracker class... does ASP have something similar? If not... is there any way I can just iterate through all the session files on the server...?
I have a site developed using ASP, but each page I enter has a different session id when accessing the site using the domain name of the site. When accessing the site from my network and using the internal IP address, it is OK. Any ideas?
I wrote a website, which uses the session to store and track some vars.
Now I am gonna to covert it to desktop application by Activesite compiler 5, however, it doesnot support session , cookie , application() . SO ,I have no idea to find something can instead of session.
My orignal processing: Session -> modify Session var -> store to Database.
There is a problem about ASP session ID. ASP session is implemented by storing session id in a session cookie, but I read this cookie in ISAPI Filter, get a string as following: ASPSESSIONIDQADCQQTS = IAOFCBBCGDGMDGCNJIKPNBAN
But the real session ID is 554851848. (Real sessionID is sessionID property the ASP session object)
Problem is what is relation between them? And how to get real session ID from cookie session ID.
I did a session("adminlogin")=1, if I post it to the same page, it returns true. But if I response.redirect to another page. This value doesn't exist anymore. This is on the actual server where all the ms security is updated.
The same script worked okay on my test server (the security patch not patched yet.)
Has anyone encountered this? How do you overcome it?
I tried searching the net it says the problem lies with a ms security patch. How I wish I can unintall that patch.
I have asp and asp.net web application. When I run it in IE7 in first tab it starts a new session. When I open second tab and browse to the same site the new session is not started (infact I need to have new session there).
Whereas, 2 IE instances generate 2 unique sessions. Only issue is with IE tabs. Firefox also has similar things but lets not talk about firefox here. I am more concerned with IE only.
In my login script I set session("User") = rs("User") the session timeout is set to 20 min
Do I need to setup some kind of update session variable on each page so that the timeout does run out or does iis update the variable aslong as I'm browsing the website ?
And another thing, <% application("something") %> works fine on my test server but once I implement it onto the main webserver I dont get any text out, is there some kind of switch that enables this function ?
My buttons default as you can see in the code. But I now want to take what is already choosen in database and chose apropriate button. Can I use a session to choose a radio button? Code:
I am using the session(loggedin) to see if a user is logged into that section of the site. The problem is that it is timing out on them, is there a way to define the length of the session (I think it times out at 10 or 20 mins currently), but to extend it to an hour or so. Any thoughts.
I've developed a shopping cart app in ASP, to secure transaction by SSL, it 've put only the checkout page in SSL but all other pages i.e. product, cart etc remains on non SSL connection. How can I track user session from non SSL to SSL checkout page as the SessionID changes when shifting to SSL (to prevent session stealing/ hijacking). I'm tracking user session by putting SessionID in cart DB with products. Given below the preview of cart table ....
I have a page that a user is logged in via a session that displays a thumbnail of a picture. The picture is a link to the full size image. When there is no target="_blank" in the code, it works fine.... except it needs to open in a new window. When I add target="_blank" the new open browser window seems to act as a whole new session (even though no session.abandon or anything had been called). I need it to keep the session, but in a new window. What do I need to do, and why is it doing this? Is a JavaScript window opener the (only) way to go?
I'm building a Shopping Cart, but then right away i've stumbled on a little problem. I need to Hold things a costomer is buying in a session. However I can't declare Session as an Aray.
Session("item_id")(2) doesn't work- right? So i was thinking maybe I can create an aray, and then somehow hold it's reference in a session("item_id"). I will apreciate if someone can show me how to save aray into the session, and how to extract it from there later on.
I'm setting up 2 websites for a friend of mine, en I'm have problems with one of the sites.The situation: I have 2 different domains (both in the .NL domain). Both domains provides the possibility for users to log in. The loginscript and the databases are hosted at server 1. The site at server 2 contains a link to the loginpage at server 1. That works well... so far. The problem is that when I log in at server 2, he doesn't accept it. I found out that the Session variable I use isn't recognised. I use Session("protected") to keep track of the users who are logged in. When there credentials are right according to the database, Session("protected")=True and the loginpage gives a redirection to partner.asp by doing Response.Redirect "partner.asp". Trying to log in from server 1 works fine, trying to log in from server 2 doesn't. My questions therefore are: 1. Is the Session variable rememberd by server 2 (although server 1 contains the loginpage en gives a redirection to a page on server 1) 2. What can I do to correct this problem? Your answers are appreciated, and sorry for the possible worse language in this message (English is not my native language ;))
Once a user logs in, I created a session.After he logs out and if he clicks the back he should not see the previous pages and only should be redirected to the main.asp
I am trying to create a login for my webpage so that certain sections are protected. Now, I have the basic login script up and working.the problem comes in recognizing when a user has logged on and when they have not.How would I approach this?
I have read some documentation and it seems that I have to create an application and start my session for each user in there once they successfully log on, but I can't find out HOW to do this.
Does any one known any good websites or links that explain how sessions are used and modified?Had a look already but they all seem pretty complicated and dont explain whats going on?
how I check whether a session is dead based soley on the Session.SessionID. At present the timeout is set to 20 minutes in IIS, I am aware that I can reset this on the page. However after 22 minutes, or some interval longer than the session timeout, the Session.SessionID values is still availible.
What I want to achieve is this. There is a small section of my site that must have an active session. When a user enteres this part of the site I must check if the session is still active because I am going to want to create variable in the sesion object. If the session is dead, I have to figure out how I am going to handle this.
I am thinking I could either bring the session back to life, is this possible?? or use some sort of client side script to open a new window.