Re: [ServiceWorker] should Cache support VARY:*,otherheader or only VARY:* (#656)

> What do you mean by 'reject' -- i.e., is that an exception, silent failure...?

Reject the promise.  This is something they can catch and handle.

If we make VARY:* act like normal http caching, then we can never pull it back out with .match() or .matchAll() without using the ignoreVary flag.

Or we keep the current behavior where we do VARY matching, but just ignore VARY:*.  This seems confusing to me (on top of an already confusing algorithm) because it behaves differently from other places VARY is used.

Rejecting the promise if a VARY:* response is put in the Cache keeps the "not cacheable" behavior and leaves open the possibility of relaxing this restriction in the future.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/656#issuecomment-87887186