You can manipulate the HTML of the Web page that is about to load in your revBrowser instance, and thus add a JS function to that Web page. The function can set the cookie that you need. You can call the function either from the onload trigger in the body tag, or by calling it from LC.
Slava > -----Original Message----- > From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode- > boun...@lists.runrev.com] On Behalf Of Terry Judd > Sent: Tuesday, July 19, 2011 12:39 AM > To: How to use LiveCode > Subject: Adding cookies to RevBrowser > > My university has just implemented a Single Sign-On service which is > probably a good thing for most but breaks all my existing routines for > authenticating against the university library (to allow me to display > library resources either in a revBrowser instance or in the user¹s > default > browser). > > Anyway, I can apparently request a token (by posting a username and > password > combination to a particular url) and use this to set a browser cookie, > which > should then allow me to avoid displaying an SSO login screen to the > user > when they first try to access a library resource. Can someone give me > some > clues as to how I go about manually setting a named cookie for > RevBrowser > and/or the user¹s default browser? > > Cheers, > > Terry... > > -- > Dr Terry Judd | Senior Lecturer in Medical Education > Medical Education Unit > Melbourne Medical School > The University of Melbourne > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
