In many ways, preserving session state makes sense– without it, users are likely to find that their restored tabs are immediately navigated to a login page when the browser is restarted. In contrast, the Firefox/Chrome/Edge76+ settings restore the browser session itself… which means that closing the browser does not delete your session cookies and doesn’t empty the HTML5 sessionStorage. The Internet Explorer and Edge 18 settings simply open tabs to the URLs of the tabs that were open when you last closed your browser. …and the old setting from Edge 18 (Spartan) and earlier: …both behave very differently than the old setting from Internet Explorer:
Until last week, I didn’t realize that these browser settings in Chrome/Edge76: So how did this zombie cookie live so long? In contrast, many Persistent cookies are configured to last for a year or more. Now, in most cases, developers expect that Persistent cookies will live longer than Session cookies– most users restart their browsers (or computers) every few days, and many modern browsers require restart (to install updates) every few weeks.
Recall that there are two types of cookies: That post was written in response to a compatibility problem with some internal web application that could somehow get in a state where a single “bad” cookie would cause the application to fail to load. The team that owns the application later looked into things further and discovered that the problem was that the application was misbehaving upon receipt of a very old (over a month) session cookie. I’ve been working on browsers professionally for 12 of the last 15 years, and in related areas for 20 of the last 20, and over the years I’ve discovered enough surprises in browser behavior that they’re no longer very surprising.īack in April, I wrote up a quick post explaining how easy it is to delete a single site’s cookies in the new Edge browser.