This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22414 - 304 handling
Summary: 304 handling
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard: blocked on implementers weighing in
Keywords:
Depends on: 26423
Blocks:
  Show dependency tree / graph
 
Reported: 2013-06-20 08:18 UTC by Anne
Modified: 2014-10-13 15:27 UTC (History)
4 users (show)

See Also:

Attachments

Description Anne 2013-06-20 08:18:08 UTC 
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.
Comment 1 Hallvord R. M. Steen 2013-06-21 08:30:09 UTC 
Anne, what about continuing the work in https://www.w3.org/Bugs/Public/show_bug.cgi?id=12607 ? ;-)
Comment 2 Anne 2013-06-21 08:53:16 UTC 
http://krijnhoetmer.nl/irc-logs/whatwg/20130621#l-316 onwards has more information.
Comment 4 Anne 2014-10-13 15:27:53 UTC 
https://github.com/slightlyoff/ServiceWorker/issues/412

Closing this in favor of the GitHub issues. It's mostly fixed now anyway.