I don't know anything about Xojo, but from the code you posted all it seems to do is set a value on the server and immediately read it back. There is no way for the browser to have it yet. The browser only sets a local cookie from a HTTP response containing a "Set-Cookie" header. If cookies are enabled, the *next* request to the same server (with conditions related to the url) will have a "Cookie" header with the value from the previous request. If you wanted to do this in what *appears* to be a single page request, your initial request to the server could return some Javascript that immediately calls back to the server with the cookie value (or reports it not found). Of course, via Javascript, you could also check for the cookie and complain to the user directly that cookies are off without ever reporting the status back to the server.
John DeSoi, Ph.D. > On Jun 5, 2018, at 3:51 PM, JOHN BAUGHMAN via 4D_Tech <[email protected]> > wrote: > > I will be exploring further why Xojo is seeing the cookie when in fact it has > not been set. I suspect that it is not really reading the cookie from the > browser but instead storing the cookie value for the duration of the current > request. Perhaps it has to, since it really cannot be read from the browser > yet. ********************************************************************** 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:[email protected] **********************************************************************
