Mark Nottingham
Mark Nottingham
Fetch also says: > If header list contains `If-Modified-Since`, `If-None-Match`, `If-Unmodified-Since`, `If-Match`, or `If-Range`, fetch will set cache mode to "no-store" if it is "default". This means that if the...
I created some tests for the current spec; it looks like Safari passes all, Chrome has one error (it sends `Cache-Control: no-cache` instead of `max-age=0` when the mode is `no-cache`)...
This is really an API / client decision; if you want to be 'helpful' to the user, you try to guess what they intend (as Fetch currently does), while if...
Yes, I think the proposal is to remove what are now (17) and (18) from [http-network-or-cache-fetch](https://fetch.spec.whatwg.org/#http-network-or-cache-fetch): > 17. If httpRequest’s [cache mode](https://fetch.spec.whatwg.org/#concept-request-cache-mode) is "no-cache", httpRequest’s [prevent no-cache cache-control header modification...
> I believe most http caches only store one entry per URL, so this would evict the target url as well. Just browser caches.
Anne AIUI most of your current testing regards what's reflected in JS and in the UX, not on the wire, correct?
@ethanresnick they're on the queue.
Not sure - why am I CC:ed?
Things that have meaning (to some) being swallowed silently makes me nervous -- I think I agree with you @annevk that failure is the better option.
Thanks. What is "output file" in the context of a linter?