Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

session management

 
muthulingam Jayakanthan
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I cant understant the following statments. pls explain whixh is corerect

A. If the web application uses HTTPS, then the web container may use the data on the HTTPS request stream to identify the client

B. The sessionid cookie is stored permenantly on the client so that a user may return to the web application and the web container will rejoin that session.
 
Nitish Bahadur
Ranch Hand
Posts: 118
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A is correct. HTTPS support in a Web Container allows you to enable SSL ID Tracking, which is one of the 3 ways you can simulate stateful HTTP Sessions.

B I think is wrong. By default Cookies are not persistent, unless you make it persist by setting the age. Additionally, Session ID changes when you invalidate the session. Storing the ID on the client is not going to help.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic