[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 #8 from mark.hughes at green-ant.com  2008-03-24 09:02 PDT -------
> > Note: As a point of comparison, repeat the same thing in FireFox with FireBug
> > installed. On reload, ONLY the HTML page is reloaded from the network.
> 
> In general, Safari reloading behavior should be compared to what other browsers
> do on Shift-reload - since we only have on flavor of reload, it has to be the
> more thorough one.

All due respect to the many engineers who have spent their time working on this
project, but that doesn't sound like a proper implementation of the mechanism.
Most all browsers seem to implement "Specific end to end" on reload, as
referenced earlier. That WebKit would forcibly ignore the cache on reload seems
counterintuitive, and unfriendly to the types of issues I list above - low
bandwidth, high latency, or resource-limited devices - the first two I have
spent much time in, and I am made to shy away from WebKit/Safari when I do.

That said, what is the rationale for wholesale reloading on "reload?"


-- 
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.