I tried using a page and using a $$NavigatorTemplate launch form. Neither
method allows me to grab a cookie when using this launch method without
explicitly calling the design element in the url: "http://domain.com/db.nsf" or
"http://domain.com/db.nsf?open" does not work. But
"http://domain.com/db.nsf/WebLaunch?OpenNavigator" does work.
The only cookie returned when calling just the database is the DomAuthSessId.
When the weblaunch is called, the existing cookie and the DomAuthSessID are
both returned, which is what I expect. Server is 5.0.10. I also tried turning
off Single Server authentication with same results.
Has anyone run into this? Is this a bug? Am I not doing something right? Any
thoughts on a work-around? I would prefer not having to tell clients to put the
design element names in the url.
I tried using a page and using a $$NavigatorTemplate launch form. Neither method allows me to grab a cookie when using this launch method without explicitly calling the design element in the url: "http://domain.com/db.nsf" or "http://domain.com/db.nsf?open" does not work. But "http://domain.com/db.nsf/WebLaunch?OpenNavigator" does work.
The only cookie returned when calling just the database is the DomAuthSessId. When the weblaunch is called, the existing cookie and the DomAuthSessID are both returned, which is what I expect. Server is 5.0.10. I also tried turning off Single Server authentication with same results.
Has anyone run into this? Is this a bug? Am I not doing something right? Any thoughts on a work-around? I would prefer not having to tell clients to put the design element names in the url.
Thanks for any help on this.