> On Jun 5, 2018, at 12:28 PM, Jim Labos - infobase via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > I think that it's a question of the Browser not actually creating the Cookie > until 4D ends the connection/method. If one traces the browser's actions one > only sees the Cookie existing only after 4D sends the response but not > before that. Upon the next connection there is no problem reading the > Cookie.
The browser does not create the cookie until it receives your first response that contains a Set-Cookie header. There is no way for you to verify they have cookies enabled/disabled until they make a *second* request where you can see if your value is in the Cookie header. John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************