The way that authentication is done is using a special return in HTTP (401: Unauthorized). That dialogue can be brought up at different points, but once it is entered, I don't see how you can ask the browser to get rid of it. The people who designed HTTP were probably not worried about that functionality; they left it up to the browser to decide whether to keep it stored between sessions. That's probably why so many people use cookies instead. With cookies, you can tell the browser that the cookie should be lost after the browser is quit.
Peace and Luck! Je77 On Mon, Feb 06, 2006 at 03:42:57PM -0600, Dan Ringrose wrote: > Hi! Thanks for thinking on this. I like the suggestion of using > aniwebs, except that we've got a lot invested in customized swiki css > design/template (which has to be split into all sorts of files - > before buttons, after buttons, etc.) for our classes and I'd rather > not have to learn how to do this all over for the schemes used in the > aniani wikis. > > I am not proficient enough at swiki/smalltalk coding to know if this > might work, but what I wondered was if the code that processes the > Edit request could be changed somehow to bring up the authentication > box. It must somehow check to see if a user has already logged in. > Could a version _not_ ever check this, instead assuming the user > isn't valid, which would bring up the login box? Once the user logs > in he could be directed to the swiki home page instead of editing. > The modified code might be saved as a "authenticate" script. > > Bear with me, as I am out of my depth on the coding side of things > here, but perhaps this makes sense. > > If this can't be done, let me know. > > Dan > > > On Feb 6, 2006, at 3:28 PM, Jochen F. Rick wrote: > > >Hmm. I've been looking and can't seem to find a solution. The HTTP 401 > >code is not really customizable. That's probably why Web developers > >have > >migrated away from it to using cookies. > > > >Peace and Luck! > > > >Je77 > > > >On Sat, Feb 04, 2006 at 11:04:04PM -0600, Dan Ringrose wrote: > >>Fellow list members - here's my current swiki quest: > >> > >>One way we've deployed swikis is on wireless laptops used in > >>different class settings. Usually the laptops are put to sleep after > >>each session, often with all the programs running, including the > >>browser. Unfortunately, this means that often those browsers > >>"remember" the last login info for particular swiki pages, which is > >>less than ideal with shared equipment. > >> > >>Can anyone suggest a way to include a "log out" button on each of my > >>swiki pages? I'd like it to bring up the username/password dialog. > >>This would make it easy to switch between authenticated users on the > >>same machine, or for me to login with higher level authority, make > >>changes, and then log out. One might also think of this button as an > >>"authenticate" button. I'm looking for an alternative to clearing > >>the browser cache, quitting the browser, and restarting it each time > >>- a task that is different on each browser and not intuitive to most > >>of my users. > >> > >>Any thoughts? > >> > >>Thanks! > >> > >> > >> > >> > >>Daniel Ringrose, Department of History, Minot State University, > >>Minot, ND > >>email: daniel.ringrose at minotstateu.edu > >> > > > >>_______________________________________________ > >>Pws mailing list > >>Pws@cc.gatech.edu > >>https://mailman.cc.gatech.edu/mailman/listinfo/pws > > > > > >-- > >Jochen "Jeff" Rick, PhD Candidate, Georgia Tech College of Computing > >[EMAIL PROTECTED], http://www.je77.com/, work: 404-385-1105 > >_______________________________________________ > >Pws mailing list > >Pws@cc.gatech.edu > >https://mailman.cc.gatech.edu/mailman/listinfo/pws -- Jochen "Jeff" Rick, PhD Candidate, Georgia Tech College of Computing [EMAIL PROTECTED], http://www.je77.com/, work: 404-385-1105 _______________________________________________ Pws mailing list Pws@cc.gatech.edu https://mailman.cc.gatech.edu/mailman/listinfo/pws
