Hi,
yes, I tryed to 'unset' the cookie. I canceled managing my attention with cookies...
But there are still some questions left, because of this funny effects.
1.) Request take longer time.
2.) When the cookie was set/unset, I parsed
the hole disk to find out, where the enttry,
which was set within the cookie, allready is available.
- webserver runs under Linux, here I could't find the value, that was intended and ok.
- cient - win 2000, sometimes the entry in cookie was visible, sometimes not.
When I deleted the entry in cookie by myself, I expected the server has no rights of access
even if the last instance of the browser was closed.
But sometimes (as long as cookie is not expired) the server sets a cookie with the value of the deleted cookieentry... After searching the whole clientside disk, I just found it in profile.sys (Im not fit in Win2000, but it has to do with swap?), which you can't read and I didn't dare to delete this file. And I found it in netscape.hist. In which I also deleted all passworvalues. For me I was a silly thing to follow up that matter.
But few question are still left, I.)where gets the server the passwordvalue? II.) How can I cookies rearly delete, tha the server has no access?!?
Handling with sessions is much easier, there are more possibilities.
3.) Solution with cookies doesn't fit to our companys security agreements.
I managed it with sessions again, and within the session the password is crypted and decrypted when I need it for a bind. Secure transfer can be mangaged via https, so users don't havt to authentificate again.
Tanja