[11531] in www-talk@info.cern.ch
Re: Enforce reloading of page when using the back-button
daemon@ATHENA.MIT.EDU (Kevin J. Dyer)
Thu Mar 9 19:31:45 2000
Date: Thu, 09 Mar 2000 19:25:25 -0500
From: "Kevin J. Dyer" <kdyer@draper.com>
In-Reply-To: <38C73464.94C9C150@w3.org>
To: Dan Connolly <connolly@w3.org>, grahame@melb1.kestral.com.au
Cc: www-talk@w3.org
Message-Id: <4.2.2.20000309191426.00cc01c0@imap>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-From: www-talk@w3.org
Dan,
I thought this section was only applicable to proxies and intermediate
caching servers / services? Even if it is applicable to the User Agents,
If the response reached the requesting agent then, IMHO, it is considered
to be a private (non-shared) cache and will therefore cache the page. I
haven't found any reference that indicates what a User Agent should be
considered, or how one might reset one.
Kevin
At 12:19 AM 3/9/00 , Dan Connolly wrote:
>Actually, I find quite explicit protocol support in HTTP 1.1 for this
>case:
>
>"private
> Indicates that all or part of the response message is intended for
>a single user
> and MUST NOT be cached by a shared cache. This allows an origin
>server to
> state that the specified parts of the
> response are intended for only one user and are not a valid
>response for
> requests by other users. A private (non-shared) cache MAY cache the
>response.
>
> Note: This usage of the word private only controls where the
>response may be
> cached, and cannot ensure the privacy of the message content. "
>
>-- http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1
>
>Again, I think your issue is with User Agents that lack support for
>this sort of thing.
===========================================================
Kevin J. Dyer Draper Laboratory MS 35
Email: <kdyer@draper.com> 555 Tech. Sq.
Phone: 617-258-4962 Cambridge, MA 02139
FAX:
617-258-2061 http://www.draper.com
----------------------------------------------------------------------------
------------------------------------------
_/_/_/_/ _/ _/ _/ _/ _/ _/_/_/_/
_/ _/ _/_/ _/_/ _/ _/_/ _/ _/
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/_/_/_/ _/ _/ _/ _/ _/ _/ _/_/_/_/
Data Management & Information Navigation Systems
===========================================================
