Earl Fogel wrote:
>
>On Mon, 7 Oct 1996 Christian Balzer <cb@brewhq.swb.de> wrote:
>
>>However people who think that the latest Dilbert strip has
>>to be out now can and will hit the "Reload" button, a lot. Right now
>>I estimate that about 20-30% of the external accesses are TCP_REFRESH
>>requests of perfectly valid data. An option to Squid which allows
>>these requests to be transformed into an IMS/size check procedure would
>>greatly reduce this load.
>
>Yes, please.
>
>Also, when you hit Reload, Netscape includes a Pragma: no-cache HTTP header
>in the request, and squid doesn't service the request from it's cache. I'd
>think that's the correct behavior for GET requests, but when a request
>includes both an LMS and a Pragma: no-cache, *and* squid has a cached copy
>of the document that's newer than the one the browser has, then I think
>squid should return it's cached copy.
>
>So, hitting Reload would always give you a newer copy of a document
>(if one is available), but it wouldn't necessarily give you the newest
>copy.
>
Well, if somebody did hit Reload it's only fair to check at the source (but
using IMS/size check if possible and not transfering everything again),
once a cache is trusted by the users to be current enough by itself the
reloads will drop...
>>Incidently I do see some TCP_IMS_HIT in the
>>access logs, so some browsers must be doing things more sensible
>>than Netscape (or am I missing something obvious here?).]
>
>I've been told that MSIE does not include the Pragma: no-cache header
>on Reloads.
>
True, in an ideal world Netscape would use a complete IMS check on
simple reload and the no-cache header on shift-Reload...
Mata ne,
<CB>
-- // <CB> aka Christian Balzer, Tannenstr. 23c, D-64342 Seeheim, Germany \X/ CB@brewhq.swb.de | Voice: +49 6257 83036, Fax/Data: +49 6257 83037 SWB - The Software Brewery - | Team H, Germany HQ | Anime no OtakuReceived on Wed Oct 09 1996 - 00:17:13 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:33:15 MST