22414 2013-06-20 08:18:08 +0000 304 handling 2014-10-13 15:27:53 +0000 1 1 1 Unclassified WHATWG Fetch unspecified PC All RESOLVED FIXED blocked on implementers weighing in P2 normal Unsorted 26423 1 annevk annevk hsteen mike mnot public-webapps sideshowbarker+fetchspec oldest_to_newest 89641 0 annevk 2013-06-20 08:18:08 +0000 Currently XMLHttpRequest has a way of opting into 304 handling by using certain headers. However, it's not clear whether that's well implemented. We should probably make it clearer how this is actually supposed to be implemented. The way to solve this is probably by passing some parameter to Fetch to have it either return the cached copy or the 304 directly. That will also give better control to new HTTP APIs. 89686 1 hsteen 2013-06-21 08:30:09 +0000 Anne, what about continuing the work in https://www.w3.org/Bugs/Public/show_bug.cgi?id=12607 ? ;-) 89688 2 annevk 2013-06-21 08:53:16 +0000 http://krijnhoetmer.nl/irc-logs/whatwg/20130621#l-316 onwards has more information. 109663 3 annevk 2014-07-31 14:41:14 +0000 https://github.com/slightlyoff/ServiceWorker/issues/398 113026 4 annevk 2014-10-13 15:27:53 +0000 https://github.com/slightlyoff/ServiceWorker/issues/412 Closing this in favor of the GitHub issues. It's mostly fixed now anyway.