[Webkit-unassigned] [Bug 82291] Pages containing "multipart/x-mixed-replace" resources should not be cached.

[bugzilla-daemon at webkit.org]

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





--- Comment #12 from Chris.Guan <chris.guan at torchmobile.com.cn>  2012-03-28 19:08:15 PST ---
(In reply to comment #10)
> To add a further point of clarification on the very premise of this bug:
> 
> In general we should work to fix any exemption to the page cache on a case-by-case basis.
> 
> Some of the reasons a page can't be cached are policy decisions: HTTPS with certain caching headers, for example.  We have to maintain those exemptions to keep financial institutions happy, for example.
> 
> But *many* reasons on the list of exemptions are *current* technical shortcomings that we should strive to solve.
> 
> This "multipart/x-mixed-replace" issue is a technical one.  Currently we have no acceptable solution for caching such a page then restoring it: Images would be frozen mid-frame, for example.
> 
> But there are clever solutions we implement in the future.  Replace the image with a paused frame that could be gracefully resumed automatically or by explicit user action to re-establish the network connection, for example.
> 
> Once we get this bug resolved in a proper cross platform manner we need to make sure to have a bug tracking "Remove the multipart/x-mixed-replace exemption by gracefully allowing such resources in the page cache"

Thanks a lot. It is reasonable and I understood.

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