- From: <bugzilla@jessica.w3.org>
- Date: Thu, 20 Jun 2013 08:18:08 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22414
Bug ID: 22414
Summary: 304 handling
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: XHR
Assignee: annevk@annevk.nl
Reporter: annevk@annevk.nl
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 20 June 2013 08:18:09 UTC