C
Chris Newby
I have a site that is using Basic authentication to validate users against
an NT domain. The site has a "log off" feature, however without forcing the
browser window to close, I don't know how to make the browser "uncache" the
user's credentials. Ideally, the process flow would work as follows:
- User requests a page from a secure part of the site
- User is asked to submit credentials
- User is validated and allowed into secure part of site
- User clicks "logoff" and is directed to an unsecured log off page
- User requests a page from a secure part of the site
- The process iterates
As of now, in the log off page I've tried sending an HTTP status of "401"
and i've tried sending a "WWW-AUTHENTICATE" HTTP header. But neither has
thus far had the desired effect.
Any suggestions are welcome.
TIA//
an NT domain. The site has a "log off" feature, however without forcing the
browser window to close, I don't know how to make the browser "uncache" the
user's credentials. Ideally, the process flow would work as follows:
- User requests a page from a secure part of the site
- User is asked to submit credentials
- User is validated and allowed into secure part of site
- User clicks "logoff" and is directed to an unsecured log off page
- User requests a page from a secure part of the site
- The process iterates
As of now, in the log off page I've tried sending an HTTP status of "401"
and i've tried sending a "WWW-AUTHENTICATE" HTTP header. But neither has
thus far had the desired effect.
Any suggestions are welcome.
TIA//