[Webkit-unassigned] [Bug 17998] When a resource is cached locally, WebKit should follow RFC 2616 "Specific end-to-end revalidation" instead of "Unspecified end-to-end revalidation"

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=17998





------- Comment #9 from ap at webkit.org  2008-03-24 09:22 PDT -------
Please note that my personal opinion is that we should have both reload and
shift-reload. But in the absence of the latter, it appears obvious that reload
should fulfill the primary purpose of reloading - which is to guarantee
freshness of content, regardless of proxy misconfiguration, time zone changes,
software bugs and other issues that may necessitate full reload. Saving
bandwidth is a very important consideration, but a secondary one.

Just as an example, in the past I've personally experienced a situation where I
couldn't reload stale content that was stuck in a proxy from within Safari - I
had to open the same page in Firefox and use shift-reload; only after that,
Safari would display updated content.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.