Quoting Davor Ocelic (suppressed):
>
> > Yes. And because the whole idea of CookieName is that you can
> > accept a cookie from some other program -- i.e. not generated
> > by IC.
>
> But then there's another problem at sight, isn't it.
>
> When I set CookieName, and visit the site the first time, the cookie
> gets created with contents being literally just 8 random
> chars (like say, "duYrlxYz").
>
> However, when you access the second page, Interchange appends
> other info to that cookie (":127.0.0.1" in my case), and with
> the default CookiePattern, the *session ID* goes along with
> cookie contents from being "duYrlxYz" to becoming
> "duYrlxYz:127.0.0.1".
IC will not set the cookie if it was already set.
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.765.647.1295 tollfree 800-949-1889 <suppressed>
Research is what I'm doing when I don't know what I'm doing.
-- Wernher Von Braun
_______________________________________________
interchange-users mailing list
suppressed
http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.