J
Jeff
....still new to .net 2005 using VB.
Do I understand correctly that the value of a session variable is actually stored in the server's ram, but relies on the asp.net
session ID cookie that temporarily is placed on the client's machine until the session ends? ...so that you can't use session
variables if the client has disabled cookies on their browser? So, this makes session vars much more secure than hidden fields,
which are transmitted to the client's browser and can be viewed simply by opening "view source." So, the hidden fields or query
string methods of passing values across pages will work with cookies disabled, but session vars won't?
Can SSL be used in cases where the client has their cookies completely disabled? If not, then I would assume that there is no
advantage (assuming adequate server ram) to using hidden fields instead of session vars where SSL will eventually be used?
Thanks
jeff
Do I understand correctly that the value of a session variable is actually stored in the server's ram, but relies on the asp.net
session ID cookie that temporarily is placed on the client's machine until the session ends? ...so that you can't use session
variables if the client has disabled cookies on their browser? So, this makes session vars much more secure than hidden fields,
which are transmitted to the client's browser and can be viewed simply by opening "view source." So, the hidden fields or query
string methods of passing values across pages will work with cookies disabled, but session vars won't?
Can SSL be used in cases where the client has their cookies completely disabled? If not, then I would assume that there is no
advantage (assuming adequate server ram) to using hidden fields instead of session vars where SSL will eventually be used?
Thanks
jeff