How do I clear SSL state in Firefox without closing active session. IE has this feature, but Firefox does not.
When browsing PKI-enabled websites, the session will timeout so ofter. To re-enable your session in Internet Explorer your Clear SSL state by going to Tools>Internet Options>Content(tab)>Clear SSL State. When this option is used, I use my Common Access Card to re-access the site.
Additional System Details
Every time Firefox opened
This started when...
Accessing the Air Force Portal
- DBsign Web Signer Plugin
- Adobe PDF Plug-In For Firefox and Netscape "9.4.4"
- Default Plug-in
- NPRuntime Script Plug-in Library for Java(TM) Deploy
- Shockwave Flash 10.3 r181
- Adobe Shockwave for Director Netscape plug-in, version 11.0
- Next Generation Java Plug-in 1.6.0_26 for Mozilla browsers
- Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
- Npdsplay dll
- DRM Store Netscape Plugin
- DRM Netscape Network Object
- User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20110614 Firefox/3.6.18 ( .NET CLR 3.5.30729)
Hi! After discussing with developers, I have filled a bug on your behalf regarding your issue. I would also like to ask you if clearing your history will solve your issue. To try this, follow the instructions in the "How do I clear my history" section in the Delete browsing, search and download history on Firefox article. This input might help us determine the next steps to take. Thanks for reporting your issue ;)
- Bug 668362 – Clearing SSL state without restarting session
Does it help if you clear the Active Logins via Clear Recent History?
I actually opened that bug, so I should know cor-el. I've considered the possibility of using Active Logins, and discussed it with some developers, their answer was that certificates might actually be stored in cache, so the most important thing now would be to determine if Clearing recent history cleans the SSL state at all.
Yes, I know that you created that bug.
I added this information here to make it easier to follow it now and maybe later when you may not have a link available (a fresh bug is easier to locate than one from months back). It is always better to have full backtracking information about issues and post the Bug number in cases like this for completion.