Hi,
I have just been playing around wit= h the [session] tag. =C2=A0
I was hoping that the = 'browserID' could be used to uniquely identify the users's brow= ser / platform, so if that changed you could perhaps ask them for additiona= l security measures - maybe a code sent by SMS etc.=C2=A0 I have seen this = used on SalesForce and a few other sites.
I create= d sessions using three browsers on the same Mac and got the following in th= e 'reserved.db'
<= i>b8209467353258d27f2103a6a9cee1a0cf3576ec368c9d58a3da63774bdab69f95816e539= cfa8b9dc7a65bdfe097d0e3 47fc3abacbfdcc8a93246650b8228f73e4e810c720711a36a06de067= 2b8b8cf4
7f3ec9a0208d0c744e81e3f23b363098923351= 1a49bfd5b51e55d6767194635b51acef8a1197f194d756a7c2877bd3f6 47fc3abacbfdcc8a93246= 650b8228f73e4e810c720711a36a06de0672b8b8cf4
3b4= 06cd34ccfc83771a24673250c2098114acffb2086f5305f90742d662b73ce4b030284d65fc1= 8bfce57e423a0d392c 47fc3abacbfdcc8a93246650b8228f73e4e810c720711a36a06de0672b8b8= cf4
It looks like the same = browserID was generated for sessions created by Safari, Chrome and Firefox.= =C2=A0 Am I missing something here, should there not be a different browser= ID for different browsers?
- Tom
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a114112fe00fa2a053f972a26-- .
Associated Messages, from the most recent to the oldest:
679 --001a114112fe00fa2a053f972a26 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have just been playing around with the [session] tag. I was hoping that the 'browserID' could be used to uniquely identify the users's browser / platform, so if that changed you could perhaps ask them for additional security measures - maybe a code sent by SMS etc. I have seen this used on SalesForce and a few other sites. I created sessions using three browsers on the same Mac and got the following in the 'reserved.db' *from to* *b8209467353258d27f2103a6a9cee1a0cf3576ec368c9d58a3da63774bdab69f95816e539c= fa8b9dc7a65bdfe097d0e3 47fc3abacbfdcc8a93246650b8228f73e4e810c720711a36a06de0672b8b8cf4* *7f3ec9a0208d0c744e81e3f23b3630989233511a49bfd5b51e55d6767194635b51acef8a11= 97f194d756a7c2877bd3f6 47fc3abacbfdcc8a93246650b8228f73e4e810c720711a36a06de0672b8b8cf4* *3b406cd34ccfc83771a24673250c2098114acffb2086f5305f90742d662b73ce4b030284d6= 5fc18bfce57e423a0d392c 47fc3abacbfdcc8a93246650b8228f73e4e810c720711a36a06de0672b8b8cf4* It looks like the same browserID was generated for sessions created by Safari, Chrome and Firefox. Am I missing something here, should there not be a different browserID for different browsers? - Tom =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Digital Revolutionaries 1st Floor, Castleriver House 14-15 Parliament Street Temple Bar,Dublin 2 Ireland ---------------------------------------------- [t]: + 353 1 4403907 [e]: [w]: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On 23 October 2016 at 20:02, Michael Davis wrote: > What about the case where a company, school or organization has its > network behind a single NAT'd address? There would be an unknown number = of > unique visitors with the same IP address, and for some companies, the sam= e > exact browser is also a requirement. > > > -MD > > > On Oct 21, 2016, at 11:55 AM, christophe.billiottet@webdna.us wrote: > > > > Yes, or you can capture the IP and reload the session without passing > anything: you just compare the IP with the stored session IP and if it > matches then you can reload the session individually for each page. Or yo= u > can use browserID. > > > > > > > > > > > >> On Oct 21, 2016, at 21:46, Kenneth Grome > wrote: > >> > >> Don't you have to pass a parameter in links and forms to make it work? > >> > >> Regards, > >> Kenneth Grome > >> WebDNA Solutions > >> http://www.webdnasolutions.com > >> Web Database Systems and Linux Server Administration > >> > >> > >> > >> On 10/21/2016 01:27 PM, christophe.billiottet@webdna.us wrote: > >>> [session] is a built-in WebDNA process that very simply allows to > build a session. Compared to a cookie, it is easier to use (You don=E2=80= =99t have > to care about the technical aspects of the cookie like date format etc=E2= =80=A6), > safer (nothing is written on the visitor side), faster (RAM based instead > of being read and written to the browser), and gives you a better control > (you can kill a session very easily, or move it from one browser to anoth= er > if necessary) > >>> Instead of just being a serial number like the [orderfile], if follow= s > without showing and keep information about the visitor. > >>> Information about a session is stored and can be used later. > >>> > >>> - chris > > > > > > > > > > > > --------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --001a114112fe00fa2a053f972a26 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable