|
-
Mar 24th, 2004, 03:41 AM
#1
Thread Starter
Hyperactive Member
ASP.net sessionState **RESOLVED**
Hi All,
Now that I have my application installed on a remote web server, session objects dont work when pages are accessed remotely. But when accessing them locally from the server itself it works perfectly. I have tried to manipulate the sessionState settings but still gives me nothing concrete... i've used the following:
<sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
cookieless="false"
timeout="20"
/>
anybody can help, thanx.
Last edited by vbud; Mar 25th, 2004 at 12:07 AM.
-
Mar 24th, 2004, 10:54 PM
#2
I wonder how many charact
you need to contact your host provider.
-
Mar 25th, 2004, 12:06 AM
#3
Thread Starter
Hyperactive Member
Guess not, its a LAN based application. Anyway got this solved, in fact when designing pages in ASP.net and using session state variables you should make sure that the addresses of pop up windows or other ASP pages are not explicitly written and should in fact be relative to the current site. Let me explain, if you have a link to another page in your site, it should rather be something like ..\..\MySecondPage.aspx instead of http://localhost/folder1/folder2/MySecondPage.aspx. The latter makes internet explorer create a new session and hence session variables are not accessible in the second page. Simple? but sometimes hard to spot when you have a large ASP.Net application.
cheers.
-
Mar 25th, 2004, 05:13 PM
#4
I wonder how many charact
Yes, every path should be relative.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|