<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - WebKit memory cache doesn't respect Vary header"
href="https://bugs.webkit.org/show_bug.cgi?id=71509#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - WebKit memory cache doesn't respect Vary header"
href="https://bugs.webkit.org/show_bug.cgi?id=71509">bug 71509</a>
from <span class="vcard"><a class="email" href="mailto:koivisto@iki.fi" title="Antti Koivisto <koivisto@iki.fi>"> <span class="fn">Antti Koivisto</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=71509#c20">comment #20</a>)
<span class="quote">> How much additional complex it would it be to implement full vary support?</span >
It would require moving the logic from network cache code in WK2 to WebCore. Memory cache entries would need to contain the varying header values.
The biggest problem is "Vary:Cookie" (which also the most common use) as cookie header is not visible in ResourceRequest and gets added magically behind the scenes by CFNetwork. Getting the value from web process involves synchronous IPC to network process and synchronous cookie storage read. Making this not a performance risk is tricky.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>