Yes, that is one of the ways I saw that the <@userreferencecookies> was not working properly.

I built a sniffer in RealBasic that performed http requests like a browser, and then looked at the value of the http Headers returned. Even if there was not search arg userref, there were times when the cookie was not attempted to be written. And my app, does not write cookies, so there is no way that the <@userreferencecookies> detected a cookie. Once I did my work around, the set cookie header was present every time, and my browser testing confirmed this. If I opened the browser preferences and watched my stored cookies, I could see when it was created, and when it was not. With the default header, if I went to a witango page without a search arg, the cookie didn't create all the time, some times it did. Most of the time it did not. As soon as I did the workaround, the cookie was created every time without fail.

Robert.

P.S. I can send you an app that will hit a url and then show you the headers returned. It is a simple app that I wrote, it does the job.


On Jan 20, 2004, at 8:08 PM, Scott Cadillac wrote:


Have you tried an HTTP Sniffer yet?

--


Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
5910 Clark Rd Suite G
Paradise, Ca 95969
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/ - http://theradmac.com/

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to