W3C home > Mailing lists > Public > www-archive@w3.org > November 2017

Re: Chrome Bug: screws up CORS by using different-origin disk cache version

From: Michael[tm] Smith <mike@w3.org>
Date: Sat, 4 Nov 2017 12:07:19 +0900
To: Sarven Capadisli <info@csarven.ca>, Tim Berners-Lee <timbl@w3.org>
Cc: Anne van Kesteren <annevk@annevk.nl>, Alex Russell <slightlyoff@google.com>, Ralph Swick <swick@w3.org>, Yves Lafon <ylafon@w3.org>, www-archive <www-archive@w3.org>
Message-ID: <20171104030719.rxe2wy36png3q7nb@sideshowbarker.net>
Sarven, Tim,

Can you confirm whether or not anybody has actually raised in issue in the
Chrome issue tracker for this? Because it seems like a genuine bug to be,
but I’ve not yet been able to find any issue that’s been filed for it.

In my experience, once somebody takes time to file an issue in the Chrome
issue tracker, discussion and action start to happen quite quickly there.
See for example https://bugs.chromium.org/p/chromium/issues/detail?id=775438


Anne van Kesteren <annevk@annevk.nl>, 2017-08-21 15:32 +0200:
> Archived-At: <http://www.w3.org/mid/CADnb78ggO64OWx7eD8Rt5phW_5=BDbd4PFgwdTnW8RAQTjgRWg@mail.gmail>
> On Sun, Aug 20, 2017 at 9:29 PM, Sarven Capadisli <info@csarven.ca> wrote:
> > * Mozilla Firefox 57.0a1, Ubuntu 17.04
> Did you file a bug? I only found
> https://bugzilla.mozilla.org/show_bug.cgi?id=682237 which seems
> somewhat relevant, but doesn't really have any analysis or tests. mnot
> wrote a bunch of web-platform-tests around the HTTP cache, but
> fetch/http-cache/vary.html is mostly passing for me (apart from a test
> which doesn't seem related). Would be good to expand that with a case
> that fails.

Michael[tm] Smith https://people.w3.org/mike

Received on Saturday, 4 November 2017 03:07:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:35:51 UTC