• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

session management

 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
Ranch Hand
Posts: 118
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
I think she's lovely. It's this tiny ad that called her crazy:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
reply
    Bookmark Topic Watch Topic
  • New Topic