- From: Shel Kaphan <sjk@amazon.com>
- Date: Wed, 10 Jan 1996 12:45:45 -0800
- To: Jeffrey Mogul <mogul@pa.dec.com>
- Cc: "David W. Morris" <dwm@shell.portal.com>, http-caching@pa.dec.com
Jeffrey Mogul writes: > Second, I think we have no choice but to leave the behavior of > a history buffer up to the browser implementor, although we might > specify that if a browser confuses the distinctions, then any > resulting erroneous behavior is not the fault of the servers or > proxies. I know we can't go too far down this path, but in order to demonstrate the importance of this subject, we might also want to point out some of the consequences of not following whatever recommendations we make. For instance, if a history buffer always tries to re-load stale pages when they are re-viewed using history mechanisms, that can cause problems for service providers and their users -- unintended side effects, to name one -- that force the service providers to change the "freshness" info they attach to responses just to work around this behavior of the user agent. Etc. --Shel
Received on Wednesday, 10 January 1996 22:32:15 UTC