<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Safari fails to clear ETag cache after 404"
href="https://bugs.webkit.org/show_bug.cgi?id=156048#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Safari fails to clear ETag cache after 404"
href="https://bugs.webkit.org/show_bug.cgi?id=156048">bug 156048</a>
from <span class="vcard"><a class="email" href="mailto:nolan@nolanlawson.com" title="Nolan Lawson <nolan@nolanlawson.com>"> <span class="fn">Nolan Lawson</span></a>
</span></b>
<pre>Clarification: by "server provides a cached response" I meant "server provides a cacheable response."
I'll also note that this could be considered a CouchDB bug rather than a WebKit bug, because if the client never gets the 404, they would never be informed that the content had changed, since the ETag never changed. And AFAICT the spec doesn't specify whether 404 should invalidate the ETag: <a href="http://tools.ietf.org/html/rfc7232#section-2.3">http://tools.ietf.org/html/rfc7232#section-2.3</a></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>