Can Session variables sometimes be blocked or otherwise corrupted by
passing through a corporate firewall?
Here's a scenario: I have a login screen where session variables are
created and then "passed" to a welcome screen. Depending on location of
where a client computer is, the variables may or may not get passed (I
found this out because the client was doing a demo from a large
university site using NS 6.2 and had this problem-threw an error, but I,
using the same browser on a small network in another part of the
country, was able to have the session vars passed successfully - I
couldn't replicate the problem on three different computers with 7
different browsers). I have the pages programmatically set not to cache
to a client's computer.
Is there something else I should be doing or not doing?
<!--- If authenticated, create session variables --->
<!--- The "GetUser" is the query from the db --->
<CFLOCK TIMEOUT="10" THROWONTIMEOUT="No" TYPE="EXCLUSIVE"
SCOPE="SESSION">
<CFSET SESSION.Auth = StructNew()>
<CFSET SESSION.Auth.IsLoggedIn = "Yes">
<CFSET SESSION.Auth.ContactID = GetUser.U_ID>
<CFSET SESSION.Auth.First_Name = GetUser.First_Name>
<CFSET SESSION.Auth.Last_Name = GetUser.Last_Name>
</cflock>
<!--- On the welcome page --->
Welcome <cfoutput><FONT
color="##000000">#SESSION.Auth.First_Name# #SESSION.Auth.Last_Name#
</FONT>.</cfoutput>
Thanks,
Mark
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
