[Webkit-unassigned] [Bug 109566] Invalid resource identifier in callbacks after a 304 response in the main resource

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Carlos Garcia Campos <cgarcia at igalia.com>  2013-02-12 11:09:21 PST ---
(In reply to comment #1)
> Is this still on trunk? I thought I had resolved this in http://trac.webkit.org/changeset/141615

hmm, looking at the patch it seems to fix the problem of reporting an invalid resource identifier, but it might still emit the callbacks in a different order, for example, the didReceiveResponse for the main resource might be called after the main frame load is committed. I haven't really tried it, though. I guess that didReceiveContentLength might also be called for the main resource after 304, which I'm not sure is right because there's no actual data transfer in such case.

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