-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b07
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2206115 | 7 | Sowmya Kannan | P3 | Closed | Fixed | b103 |
Reported by ###@###.###
In http://java.sun.com/javase/6/docs/technotes/guides/javaws/enhancements6.html
"The <no-cache> directive is now honored. If a downloaded resource
contains the no-cache directive, it will not be put in the cache"
Commented by ###@###.###
This is not correct. It should be "no-store" instead:
If a downloaded resource contains the no-store directive, it will not be put in the cache.
Reported by ###@###.###
In http://www.java.com/en/download/help/6000070100.xml
"The no-cache directive is now supported. When the no-cache directive
is used, an update check is made to make sure the cached contents are
same as at the URL. The resource is then downloaded into the cache and
the expiration field is ignored. "
Commented by ###@###.###
This is almost correct. no-cache means the cached contents cannot be
used without revalidation. So if cached content is available, an update
check will be made to ensure the server copy is the same as the cached
copy. If so, cached copy can be used. If not, server copy will be
downloaded. Expiration field is ignored, which means that even if the
cached resource is not expired, update check will still be performed.
In http://java.sun.com/javase/6/docs/technotes/guides/javaws/enhancements6.html
"The <no-cache> directive is now honored. If a downloaded resource
contains the no-cache directive, it will not be put in the cache"
Commented by ###@###.###
This is not correct. It should be "no-store" instead:
If a downloaded resource contains the no-store directive, it will not be put in the cache.
Reported by ###@###.###
In http://www.java.com/en/download/help/6000070100.xml
"The no-cache directive is now supported. When the no-cache directive
is used, an update check is made to make sure the cached contents are
same as at the URL. The resource is then downloaded into the cache and
the expiration field is ignored. "
Commented by ###@###.###
This is almost correct. no-cache means the cached contents cannot be
used without revalidation. So if cached content is available, an update
check will be made to ensure the server copy is the same as the cached
copy. If so, cached copy can be used. If not, server copy will be
downloaded. Expiration field is ignored, which means that even if the
cached resource is not expired, update check will still be performed.
- backported by
-
JDK-2206115 Java SE 6 doc inaccuracies regarding no-cache and no-store
-
- Closed
-