[Webkit-unassigned] [Bug 144386] Main resource loaded via 304 response becomes empty if reloaded by user

[bugzilla-daemon at webkit.org]

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

--- Comment #4 from Antti Koivisto <koivisto at iki.fi> ---
> Is this needed anywhere else? Does it only affect main resources? Is there
> some way to tie it more closely to other ways we have to change the request
> in a reloading situation?

Main document loading is a rare case where we have a long-lived ResourceRequest not owned by a CachedResource. The refactoring that moved us from entirely special main resource loading to CachedResources based loading (using CachedRawResource) is basically incomplete so we end up with weird special handling.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150429/0b775de9/attachment.html>