lotus

previous page: 6.1.3) I downloaded a version of Netscape's browser that is newer than version 4.05. Now, when I go to certain https web sites that used to work for me (like my bank) I get an error message telling me that "Netscape has received bad data from the server." I've been told the problem is with SSL v3 in my new browser, and that I should disable SSL v3 in my browser. What's wrong with SSL v3 in these new browsers? Should I disable it?
  
page up: Secure Sockets Layer Discussion List FAQ
  
next page: 6.1.5) Is the cached data encrypted using some key? (Netscape SSL implementation issues)

6.1.4) Do Netscape's browsers cache data on disk that has been received via https?




Description

This article is from the Secure Sockets Layer Discussion List FAQ, by Shannon Appel SAppel@consensus.com with numerous contributions by others.

6.1.4) Do Netscape's browsers cache data on disk that has been received via https?

Navigator 3.0 and Communicator 4.x have an option to allow on-disk
caching of data fetched over SSL connections. The default setting is
to not cache https data on disk.

In Navigator 2.0, documents fetched using SSL were cached in the same
way as non-SSL documents. You could use the "Pragma: no-cache" HTTP
header to disable caching for a particular page.

In Navigator 1.0, documents fetched with SSL were not cached on disk.

 

Continue to:













TOP
previous page: 6.1.3) I downloaded a version of Netscape's browser that is newer than version 4.05. Now, when I go to certain https web sites that used to work for me (like my bank) I get an error message telling me that "Netscape has received bad data from the server." I've been told the problem is with SSL v3 in my new browser, and that I should disable SSL v3 in my browser. What's wrong with SSL v3 in these new browsers? Should I disable it?
  
page up: Secure Sockets Layer Discussion List FAQ
  
next page: 6.1.5) Is the cached data encrypted using some key? (Netscape SSL implementation issues)