Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db?

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113115
interpreted = N
texte = 703 --001a113dc4ca921837053fccf477 Content-Type: text/plain; charset=UTF-8 Tom and Donovan, Thank you for your suggestions. If I may ask one more thing. I'm trying to figure out what I need to store in the cookie and in the session.db. I have the login which then looks into the users.db and verifies that the information is correct. As soon as the [showif] confirms, I write a coolie with a [cart] value and currently store the username, session ID (the [cart] value) and an expiry value - I want to use the WebDNA epoch time but have looked on the website and can't find the proper way to create this value. What kind of data do you store in your cookies and session.db? With the data I am currently storing in the coookie and session.db, I would still be doing a lookup in the users.db to get the groups the user belongs to in order to display the appropriate menus for the user. In the past when I did a login, I only saved a session cookie as I only needed to carry the user information over a few pages. Thank you for your insight. Dale On Mon, Oct 24, 2016 at 3:37 PM, wrote: > > Question #1: > > > > Does the BrowserID use any other data from the browser, such as > > the ip address for example, or anything else OTHER THAN the data > > in the mime headers? > > no > > > Problem #1: > > > > You said you're using ALL the info returned in the mime headers, > > but this appears to be a mistake, here's why: > > > > One portion of the data returned in mime headers is cookies, so if > > there are any cookie changes from one page to the next, the > > BrowserID won't match any longer. This is a real problem for me > > because I reset the cookie expire date in my admin systems every > > time another page is requested. > > cookies is not used > > > But this does NOT explain why Tom's test concluded that all three > > BrowserIDs were identical when in fact he used three different > > browsers. > > we found that [session] is broken on the server version, because of the > way the fastCGI returns the MIME Headers compared with Server version. This > will be fixed tomorrow and we will recompile. > > > > Question #3: > > > > What happens when a mismatch occurs with the BrowserID values? > > Does WebDNA default to matching something else, such as the ip > > address? If so, this explains why all three of Tom's 'from' > > fields are different but the 'to' fields are the same: > > the first column in the db includes date, time, IP, life (seconds) and the > second column browserID > They are connected together but if IP or browserID do not match anymore, > you are free take decisions using the built-in test tags. > > > > - 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 > --001a113dc4ca921837053fccf477 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Tom and Donovan,

Thank you for your sug= gestions. If I may ask one more thing. I'm trying to figure out what I = need to store in the cookie and in the session.db.=C2=A0

I have the login which then looks into the users.db and verifies tha= t the information is correct. As soon as the =C2=A0[showif] confirms, I wri= te a coolie with a [cart] value and currently store the username, session I= D (the [cart] value) and an expiry value - I want to use the WebDNA epoch t= ime but have looked on the website and can't find the proper way to cre= ate this value.

What kind of data do you store in = your cookies and session.db?

With the data I am cu= rrently storing in the coookie and session.db, I would still be doing a loo= kup in the users.db to get the groups the user belongs to in order to displ= ay the appropriate menus for the user.=C2=A0

In th= e past when I did a login, I only saved a session cookie as I only needed t= o carry the user information over a few pages.

Tha= nk you for your insight.

Dale

=


On Mon, Oct 24, 2016 at 3:37 PM, <christophe.billiottet= @webdna.us> wrote:
> Question #1:
>
> Does the BrowserID use any other data from the browser, such as
> the ip address for example, or anything else OTHER THAN the data
> in the mime headers?

no

> Problem #1:
>
> You said you're using ALL the info returned in the mime headers, > but this appears to be a mistake, here's why:
>
> One portion of the data returned in mime headers is cookies, so if
> there are any cookie changes from one page to the next, the
> BrowserID won't match any longer.=C2=A0 This is a real problem for= me
> because I reset the cookie expire date in my admin systems every
> time another page is requested.

cookies is not used

> But this does NOT explain why Tom's test concluded that all three<= br> > BrowserIDs were identical when in fact he used three = different
> browsers.

we found that [session] is broken on the server version, because of = the way the fastCGI returns the MIME Headers compared with Server version. = This will be fixed tomorrow and we will recompile.


> Question #3:
>
> What happens when a mismatch occurs with the BrowserID values?
> Does WebDNA default to matching something else, such as the ip
> address?=C2=A0 If so, this explains why all three of Tom's 'fr= om'
> fields are different but the 'to' fields are the same:

the first column in the db includes date, time, IP, life (seconds) a= nd the second column browserID
They are connected together but if IP or browserID do not match anymore, yo= u are free take decisions using the built-in test tags.



- chris---------------------------------------------------------<= br>
This message is sent to you because= you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
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 --001a113dc4ca921837053fccf477-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
  2. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
  3. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  4. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  5. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  6. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  7. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  8. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  9. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  10. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  11. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  12. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  13. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  14. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  15. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  16. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  17. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  18. [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
703 --001a113dc4ca921837053fccf477 Content-Type: text/plain; charset=UTF-8 Tom and Donovan, Thank you for your suggestions. If I may ask one more thing. I'm trying to figure out what I need to store in the cookie and in the session.db. I have the login which then looks into the users.db and verifies that the information is correct. As soon as the [showif] confirms, I write a coolie with a [cart] value and currently store the username, session ID (the [cart] value) and an expiry value - I want to use the WebDNA epoch time but have looked on the website and can't find the proper way to create this value. What kind of data do you store in your cookies and session.db? With the data I am currently storing in the coookie and session.db, I would still be doing a lookup in the users.db to get the groups the user belongs to in order to display the appropriate menus for the user. In the past when I did a login, I only saved a session cookie as I only needed to carry the user information over a few pages. Thank you for your insight. Dale On Mon, Oct 24, 2016 at 3:37 PM, wrote: > > Question #1: > > > > Does the BrowserID use any other data from the browser, such as > > the ip address for example, or anything else OTHER THAN the data > > in the mime headers? > > no > > > Problem #1: > > > > You said you're using ALL the info returned in the mime headers, > > but this appears to be a mistake, here's why: > > > > One portion of the data returned in mime headers is cookies, so if > > there are any cookie changes from one page to the next, the > > BrowserID won't match any longer. This is a real problem for me > > because I reset the cookie expire date in my admin systems every > > time another page is requested. > > cookies is not used > > > But this does NOT explain why Tom's test concluded that all three > > BrowserIDs were identical when in fact he used three different > > browsers. > > we found that [session] is broken on the server version, because of the > way the fastCGI returns the MIME Headers compared with Server version. This > will be fixed tomorrow and we will recompile. > > > > Question #3: > > > > What happens when a mismatch occurs with the BrowserID values? > > Does WebDNA default to matching something else, such as the ip > > address? If so, this explains why all three of Tom's 'from' > > fields are different but the 'to' fields are the same: > > the first column in the db includes date, time, IP, life (seconds) and the > second column browserID > They are connected together but if IP or browserID do not match anymore, > you are free take decisions using the built-in test tags. > > > > - 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 > --001a113dc4ca921837053fccf477 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Tom and Donovan,

Thank you for your sug= gestions. If I may ask one more thing. I'm trying to figure out what I = need to store in the cookie and in the session.db.=C2=A0

I have the login which then looks into the users.db and verifies tha= t the information is correct. As soon as the =C2=A0[showif] confirms, I wri= te a coolie with a [cart] value and currently store the username, session I= D (the [cart] value) and an expiry value - I want to use the WebDNA epoch t= ime but have looked on the website and can't find the proper way to cre= ate this value.

What kind of data do you store in = your cookies and session.db?

With the data I am cu= rrently storing in the coookie and session.db, I would still be doing a loo= kup in the users.db to get the groups the user belongs to in order to displ= ay the appropriate menus for the user.=C2=A0

In th= e past when I did a login, I only saved a session cookie as I only needed t= o carry the user information over a few pages.

Tha= nk you for your insight.

Dale

=


On Mon, Oct 24, 2016 at 3:37 PM, <christophe.billiottet= @webdna.us> wrote:
> Question #1:
>
> Does the BrowserID use any other data from the browser, such as
> the ip address for example, or anything else OTHER THAN the data
> in the mime headers?

no

> Problem #1:
>
> You said you're using ALL the info returned in the mime headers, > but this appears to be a mistake, here's why:
>
> One portion of the data returned in mime headers is cookies, so if
> there are any cookie changes from one page to the next, the
> BrowserID won't match any longer.=C2=A0 This is a real problem for= me
> because I reset the cookie expire date in my admin systems every
> time another page is requested.

cookies is not used

> But this does NOT explain why Tom's test concluded that all three<= br> > BrowserIDs were identical when in fact he used three = different
> browsers.

we found that [session] is broken on the server version, because of = the way the fastCGI returns the MIME Headers compared with Server version. = This will be fixed tomorrow and we will recompile.


> Question #3:
>
> What happens when a mismatch occurs with the BrowserID values?
> Does WebDNA default to matching something else, such as the ip
> address?=C2=A0 If so, this explains why all three of Tom's 'fr= om'
> fields are different but the 'to' fields are the same:

the first column in the db includes date, time, IP, life (seconds) a= nd the second column browserID
They are connected together but if IP or browserID do not match anymore, yo= u are free take decisions using the built-in test tags.



- chris---------------------------------------------------------<= br>
This message is sent to you because= you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
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 --001a113dc4ca921837053fccf477-- . dale

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Netscape v. IE (1997) [WebDNA] Query re: autonumber (2010) pop up menu's (1998) Problems with cybercash (2000) Replto in [SendMail] (2000) Help name our technology! (1997) no global [username] or [password] displayed ... (1997) That Flakey 'Brawl' thing (1997) Sorry - the list went haywire... (1998) Support ?? (1997) Bug? (1997) Help! WebCat2 bug (1997) thisurl & arguments (2000) Multiple fields on 1 input (1997) WebCatb15 Mac CGI -- [purchase] (1997) UPPERCASE (1997) Updating checkboxes made easy !!! (1998) [WebDNA] search command problem (2009) To use GREP to boldface text (2003) Caching problem... (2000)