HTTPS Caching??

[Achim Krisinger]

Hi!

Is there any possibility to force a caching of HTTPS/SSL pages with
Java Applets in them?

background: We want to change our environment to Network computers with
only a browser on it. All needed programs are HTML and/or java based.
Because we've 100 departments which are connected via 64 KB Lines, we
want to cache the java applets in the proxy cache to reduce the network
bandwidth.

Thanks for answers!!

Achim Krisinger
Stadtsparkasse Köln

[Jeff Wierer]

The short answer is NO.

Here's the caching criteria that proxy uses: (unfortunately, you cannot
customize this)
Caching Criteria
A Web object must satisfy the following criteria in order to be cached:

a.. The request must be a GET.
b.. There must be no keywords, which are typically used for basic logons.
c.. The file must be served by the HTTP protocol (objects associated with
other protocols are not cached).
d.. The HTTP response header must not include WWW-Authenticate , Pragma:
no-cache, Cache-control: Private, Cache-control: no-cache, or Set-Cookie.
e.. The date in the Expires: header field must be later than the date in
the Date: header field. The Expires: header is used in all HTTP requests to
indicate a date and time for the request to expire on the network. The Date:
header is used to indicate the date and time that the Web server received
the request. Both fields are generically returned in almost all HTTP
requests. Some Web servers indicate to downstream caches that a page should
not be cached by setting the Expires: header equal to the Date: header,
indicating that the page expires immediately. Also, setting this field to
"Expires: 0" prevents caching as well.
f.. The HTTP Result code must be 200 (success).
g.. The object must not be encrypted or protected by Secure Sockets Layer
(SSL).
h.. There cannot be an Authorization header in the HTTP request header, or
Vary in the response header.
The HTTP header may include "cookies," which allow a server to customize a
response for a particular user. Cookies are increasingly used for custom
pages or for informal (that is, not very secure) authentication. Microsoft
Proxy Server treats cookies as another optional HTTP header that is
disregarded, with the exception of the Set-Cookie header. It is assumed that
subsequent transactions after the cookie has been set can be cached, unless
any of the subsequent objects requested include headers with
cache-ineligible exception values based on the criteria in the preceding
list.

--
Jeff Wierer MVP, MCSE+Internet
Download Proxy 2.0 FAQ v.999
http://ProxyFAQ.NetworkGods.Com
http://www.geocities.com/SiliconValley/4155/
Achim Krisinger <Achim.K...@sk.koeln.de> wrote in message
news:37D660D8...@sk.koeln.de...