What is WebDNA

WebDNA is a scripting and database system designed to easily build web applications.

WebDNA and BioType

BioType service is a biometric keystroke dynamic system. It will be part of WebDNA 8.5

Download WebDNA

Download WebDNA freeware, try it and register later if you want.

WebDNA resources

The list of all WebDNA instructions.
WebDNA
Software Corporation
Search WebDNA Site
 Menu


HOME


DOWNLOADS


LEARN


EDUCATION


NEWS


COMMUNITY


STORE


SUPPORT


CONTACT

Re: Deleting Cookie Problems

This WebDNA talk-list message is from

2007


It keeps the original formatting.
numero = 68621
interpreted = N
texte = Very helpful, thank you. on 3/4/07 11:35 AM, Donovan Brooke at dbrooke@euca.us wrote: > Eddie Z wrote: >> So if the cookie names are identical but use different URLs (same domain >> name but one with www. and one without) then I have a problem then? > > > Hey Eddie, > Kinda, there are security measures. > > if you started off with www.domain.com you are setting > a limitation... so clients accessing the site with "domain.com" > will not be able to access the www.domain.com cookie. > > Setcookie docs spell it out pretty well: > > http://webdna.smithmicro.com/ref/pages.html?context=AllTags.html#SetCookie > > The only way/s to "log out" of www.domain.com when > using domain.com would be to utilize a {redirect-to-url-www.domain.com -> > setcookietohistory --> > then redirect-to-url-domain.com}... > > The way to accommodate users from both domains is to not > originally put a limitation on the domain host. Both > www.domain.com and domain.com can access a cookie where > it was set with an original domain of "domain.com". > > In your situation, I think you would have to do some > error code that, when a client can't log out when accessing > the site via "domain.com", you would redirect them to www.domain.com, > set that cookie to history, then redirect them back. Eventually > everones www.domain.com cookies would be deleted that way. > > I did a little test page that simplifies cookie behavior that may > help you.. > > You can look in your cookie manager while using the page to > see proof of what is happening..: > > http://euca.us/admin/tests/cookieset.html?flag=T > > - Donovan > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Deleting Cookie Problems ( Eddie Z 2007)
  2. Re: Deleting Cookie Problems ( Donovan Brooke 2007)
  3. Re: Deleting Cookie Problems ( Donovan Brooke 2007)
  4. Re: Deleting Cookie Problems ( Eddie Z 2007)
  5. Re: Deleting Cookie Problems ( Donovan Brooke 2007)
  6. Re: Deleting Cookie Problems ( Eddie Z 2007)
  7. Re: Deleting Cookie Problems ( Chris 2007)
  8. Deleting Cookie Problems ( Eddie Z 2007)
Very helpful, thank you. on 3/4/07 11:35 AM, Donovan Brooke at dbrooke@euca.us wrote: > Eddie Z wrote: >> So if the cookie names are identical but use different URLs (same domain >> name but one with www. and one without) then I have a problem then? > > > Hey Eddie, > Kinda, there are security measures. > > if you started off with www.domain.com you are setting > a limitation... so clients accessing the site with "domain.com" > will not be able to access the www.domain.com cookie. > > Setcookie docs spell it out pretty well: > > http://webdna.smithmicro.com/ref/pages.html?context=AllTags.html#SetCookie > > The only way/s to "log out" of www.domain.com when > using domain.com would be to utilize a {redirect-to-url-www.domain.com -> > setcookietohistory --> > then redirect-to-url-domain.com}... > > The way to accommodate users from both domains is to not > originally put a limitation on the domain host. Both > www.domain.com and domain.com can access a cookie where > it was set with an original domain of "domain.com". > > In your situation, I think you would have to do some > error code that, when a client can't log out when accessing > the site via "domain.com", you would redirect them to www.domain.com, > set that cookie to history, then redirect them back. Eventually > everones www.domain.com cookies would be deleted that way. > > I did a little test page that simplifies cookie behavior that may > help you.. > > You can look in your cookie manager while using the page to > see proof of what is happening..: > > http://euca.us/admin/tests/cookieset.html?flag=T > > - Donovan > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Eddie Z

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:

Customizing WebDelivery.html (1998) Using Communigate Pro on Mac OS X Server (2000) Webcatalog Future?!? (2000) Price characteristics? (1997) WebCat2b12--[searchstring] bug (1997) [WebDNA] Dynamic vertical columns (2008) [WebDNA] RESTART WebDNA (2016) Math Enhancement Request (2004) re:check boxes (1997) Loop code problem (2000) RE: PIXO support (1997) WebCatalog2 for NT Beta Request (1997) WebCat2: Items xx to xx shown, etc. (1997) Open Source (2000) RE: strip .0 off off IPaddress (1998) taxTotal, grandTotal (1997) RE: error count with $purchase (1997) Need relative path explanation (1997) WebDelivery downloads alias, not original ? (1997) Semi-OT SSL IE problem (2005)