Re: [whatwg/fetch] Define a cache for H2 server push & friends (#354)

(I'm really fuzzy on which origins we're talking about being the "same" here.  There is a page origin, the request origin, and the origin of the pushed resource. All are potentially relevant in this context.)

I'm looking at fetch and it doesn't appear to be that there is any problem.  I agree that there are many reasons for withholding a request, but they can all be reduced simply by observing two things:

1. Sites can cause the browser to make a request.  This is no different to generating a push promise.

2. The existence of a response does not need to mean that the response needs to be used.  Thus, all the blocking, service workers, and other conditions can easily apply before consuming the response.  Worst case, the request needed a preflight; so send the preflight and hope that that was pushed as well.

I appreciate the caution, and the reasons, and the need to make some changes to accommodate the above model (if you accept that it is valid).  However, I don't think that those reasons are strong enough to say that you categorically don't cache pushed resources.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/354#issuecomment-282600510