Mark Leone wrote:
The point is that IE is not providing the resource to the user *the
first time* because there is a no-cache directive associated with it.
IMO there is noting in the HTTP spec that even hints that this is how
the no-cache directive is to be used. If IE needs to temporarily store
the resource in order to provide it to the user, and a no-cache header
is present, then it should find a way to give it to the user without
caching it (which of course is not the same thing as temporarily
storing it for spooling purposes), instead of refusing to let the user
see it the first time the server sends it, and then hiding behind the
HTTP spec to justify a poor implementation.
I think the end result speaks for itself. What possible use could a
no-cache directive have if it means that user agents can't even give
the resource to the user the first time it's requested? If this is
really what the spec means, then every non-cacheable resource on the
web is a self-licking ice-cream cone. Probably tastes great, but no
one will ever really know. All the other user agent implementers seem
to have interpreted the spec appropriately, without failing to give
the users the resource the server explicitly provided to them.
Maybe IEs implementation existed before HTTP 1.1 and before the
"no-store" option was introducted, which seems to clarify the matter of
what isn't allowed to be stored to disk, there is nothing else in the
specififcation that mandates the user-agent or cache can not (in the
process of serving the orginary request) store it to disk (if the
implementation needs to). From the HTTP spec point of view caching is
"just an observable concept", I make this statement to disconnect it
from the presumption it has anything to do with storing to disk or not.
I agree with you on what possible use could no-cache be within IE if
implemented their way.
I've worked with dynamic HTML for quite a few years and can't remember
stumbling over this problem, what is the simplest server response that
triggers this problem in IE ?
Darryl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
