It works even if you use incognito mode in Chrome. So incognito is not as incognito as we thought.
Edit: not really, the article explains it but I hadn't finish reading it.
Edit: not really, the article explains it but I hadn't finish reading it.
I believe the incognito mode has more potential than it's currently being used as. For example multiple parallel sessions would be not only nice and handy, if people learned to use it, the isolation would also enhance browser security. As I mentioned on the page, it single-handedly eliminates a number of https attacks and tracking methods.
Edit: Oh you mean that bug in this demonstration? Yes that's a local issue here. In practice the two sessions could not be linked, as you can see when you press f5 in the incognito window. Sorry about that, it's mostly meant as a tech demo where people can understand and learn from the code, not a finished product!
Chrome actually got this feature recently. Check Settings > Users.
1) in plain non-incognito window, enter text, hit "Store"
2) open incognito window, go to same URL, the text is there!
that means the sessions can be linked now. where does this info come from? does Chrome (and Opera, which I also tested) share ETags between non-incognito and incognito windows?
> When you visit a page where you don't have an ETag (like incognito mode), your session will be emptied.
This unfortunately also throws away your other browser session at the same time. In practice a website would probably issue a new etag for the incognito session, and your existing browser session will simply continue.
You could probably have submitted a bug to the Chrome team and get a bounty for this thing. It kind of allows to track the incognito session linking it to a normal session.