Re: [cors-tests] Add 304 tests for CORS (#1400)

We discussed this a long time ago in Webapps (IIRC). 

The upshot is that if browsers don't use the cached headers in combination with the 304's, any conditional request will fail, because intermediary caches (including those in reverse proxies, CDNs, etc.) will not be adding CORS headers to the 304. 

The applicable part of HTTP is:
  http://httpwg.github.io/specs/rfc7234.html#freshening.responses

Firefox, Chrome and Safari all pass this test right now; I haven't had a chance to try IE yet. 

Anne, I'm happy to work with you to get fetch doing the right thing here.

I can dig up the ML discussion if necessary.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/1400#issuecomment-66893664

Received on Saturday, 13 December 2014 22:13:57 UTC