[Webkit-unassigned] [Bug 73005] http-cache can break app-cache's functionality

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=73005





--- Comment #4 from Jason <liuyang12341982 at 163.com>  2011-11-23 17:58:22 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > This doesn't look like correct approach. What platform did you observe the problem on, and what was the http status code in this scenario? When network is not reachable, cache should either return a cached response (and thus not fail), or never call didReceiveResponse() at all.
> 
> I am a developer of RIM's browser. And I found this issue in our browser.
> And safari has the same issue.
> 
> http://html5demos.com/offlineapp
> when we try to view this site, webkit will preload html5demos.css, and http-cache will cache this css file.
> Then manifestParser will try to download html5demos.css again.
> But this time it will get the body from http-cache, and the status-code is 304.
> 
> In this case appCache will call cacheUpdateFailed() because the status-code is not 200.

So I don't think it is right to do this.
we should treat 304 in this case as a success because the http-body is the data appCache need.
What is your opinion?

Thanks!

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