Re: [WebDNA] User sessions - cookies only or cookies and a
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113106
interpreted = N
texte = 694 > To build the browserID, we are using all the information returned in the mime headers, like > > Accept text/html,application/xhtml xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language en-US,en;q=0.5 > Accept-Encoding gzip, ... > > Any difference, including a single dot or an extra space , would create a different browserID 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? 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. This brings up: Question #2: Does the BrowserID perhaps IGNORE use some of the data returned in the mime headers, rather than using all of it? If so, this would eliminate the problem of cookies changing on every page. But it does NOT explain why Tom's test concluded that all three BrowserIDs were identical when in fact he used three different browsers. So here's the next question: 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: My guess here is that when the second and third browserss did not match, WebDNA moved on to "Plan B" -- it tried instead to match the ip addresses. And since this succeeded, it wrote th 'second and third "from" field to match the value if the first "from" field. Is this why WebDNA thinks that all three browsers are one and the same? to match each other. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration On 10/24/2016 01:19 PM, christophe.billiottet@webdna.us wrote: > To build the browserID, we are using all the information returned in the mime headers, like > > Accept text/html,application/xhtml xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language en-US,en;q=0.5 > Accept-Encoding gzip, ... > > Any difference, including a single dot or an extra space , would create a different browserID > > - 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 .
Associated Messages, from the most recent to the oldest:
694 > To build the browserID, we are using all the information returned in the mime headers, like > > Accept text/html,application/xhtml xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language en-US,en;q=0.5 > Accept-Encoding gzip, ... > > Any difference, including a single dot or an extra space , would create a different browserID 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? 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. This brings up: Question #2: Does the BrowserID perhaps IGNORE use some of the data returned in the mime headers, rather than using all of it? If so, this would eliminate the problem of cookies changing on every page. But it does NOT explain why Tom's test concluded that all three BrowserIDs were identical when in fact he used three different browsers. So here's the next question: 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: My guess here is that when the second and third browserss did not match, WebDNA moved on to "Plan B" -- it tried instead to match the ip addresses. And since this succeeded, it wrote th 'second and third "from" field to match the value if the first "from" field. Is this why WebDNA thinks that all three browsers are one and the same? to match each other. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration On 10/24/2016 01:19 PM, christophe.billiottet@webdna.us wrote: > To build the browserID, we are using all the information returned in the mime headers, like > > Accept text/html,application/xhtml xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language en-US,en;q=0.5 > Accept-Encoding gzip, ... > > Any difference, including a single dot or an extra space , would create a different browserID > > - 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 .
Kenneth Grome
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:
Explorer 3.0/ Access Denied! (1997)
WebCat Bulletin Board Solution ? (1998)
emailer on Windows Beta 18 (1997)
2.0 Info (1997)
Round up prices (2000)
Stinkin' [Referrer] (1998)
Single Link browsing (1997)
WCS Newbie question (1997)
Many are called but only 6 make it to founditems. (2001)
shipCost -vs- shippingtotal ? (2000)
Plugin or CGI or both (1997)
MacActivity and PCS (1997)
bug in Webcat OSX (1999)
Multiple catalog databases and showcart (1997)
Ampersand (1997)
Text data with spaces in them... (1997)
Re:Realtime Transaction Processing (1999)
Attention all list readers (1997)
Writing to disk (1999)
minimalist shopping cart. (1997)