Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When you start a new browser session and browse to your site, classic ASP will detect that there is no ASP session cookie and will create a new session for you (as you have already experienced).</p> <p>Session cookies are just that, they exist for the lifetime of the session. When you close your browser the session cookie will be deleted (even though your session state on the server will live on as an orphaned session until Session.Timeout expires - unless you present the same session cookie again within the Session.Timeout period). </p> <p>The only way to extend the lifetime of the ASP session cookie across new browser sessions/instances would be to alter the cookie lifetime using script on the browser/client.</p> <p>If you're looking to manage state across events such as the browser closing, you'll need implement your own state management mechanism (persist state to a database for example) and use a regular cookie with a long lifetime (or with a sliding expiration where you extend the lifetime by a small amount of time on each request in your server side script) to match state to the user.</p> <p><strong>Edit:</strong></p> <p>The following article has a script to modify the session cookie (scroll down to Cookie Expiration):</p> <ul> <li><a href="https://web.archive.org/web/20070504042700/http://palisade.plynt.com/issues/2007Feb/asp-session-cookies/" rel="nofollow noreferrer">ASP Session Cookies (Plynt)</a>, via archive.org</li> </ul> <p>But as Shoban correctly points out there is a risk of <a href="http://www.owasp.org/index.php/Session_Fixation" rel="nofollow noreferrer">Session Fixation (OWASP)</a>. You can however go some way to protect yourself against this:</p> <ul> <li><a href="http://www.owasp.org/index.php/Session_Fixation_Protection" rel="nofollow noreferrer">Session Fixation Protection (OWASP)</a></li> </ul> <p>I'd also add some caveats, if your application is storing sensitive data (credit cards, financials, medical etc) then I'd suggest not doing this and live with the fact that your user will have to logon again and start a new session. Better safe than sorry.</p>
    singulars
    1. This table or related slice is empty.
    1. POClassic ASP Session ID Cookie Lifetime
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTomalak
    1. USKev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POClassic ASP Session ID Cookie Lifetime
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COSeems nice.... But, how to do it?
      singulars
      1. PO
      1. USDaniel Silveira
    2. CO" I'm 110% sure. Sessions DO NOT end when a user closes their browser." http://www.asp101.com/articles/john/sessionsend/default.asp Any thoughts?
      singulars
      1. PO
      1. USShoban
    3. COCorrect sessions ON THE SERVER don't end until the Session.Timeout expires, but closing the browser will cause the session cookie to expire leaving the state on the server orphaned until it's cleaned up after Session.Timeout. If there's no session cookie on the first request to the site, a new session will always be created.
      singulars
      1. PO
      1. USKev
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload