New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reuse of responses #52

Closed
mnot opened this Issue Apr 3, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@mnot
Copy link
Member

mnot commented Apr 3, 2018

The specification of no-store can be read to allow the response to be reused for another concurrent request, since it's specified in terms of non-volatile memory. Likewise, other cache directives are silent on such reuse.

So-called "request collapsing" has become quite common in proxies, reverse proxies and CDNs. Clarification as to whether such reuse for temporally concurrent requests would be helpful (in the case of no-store and otherwise).

@mnot mnot added the caching label Apr 3, 2018

@mnot mnot added the discuss label Jul 4, 2018

@jyasskin

This comment has been minimized.

Copy link

jyasskin commented Jul 18, 2018

This also seems related to preload and prefetch, which allow the response to be re-used after cache control would say not to re-use it: whatwg/fetch#590 (comment)

@mnot

This comment has been minimized.

Copy link
Member Author

mnot commented Jul 18, 2018

Discussed in Montreal; introduce the concept of a single-use response, and carve out no-store.

@mnot mnot removed the discuss label Jul 25, 2018

@mnot mnot added the has-proposal label Oct 9, 2018

mnot added a commit that referenced this issue Oct 9, 2018

@mnot mnot closed this in #150 Oct 16, 2018

mnot added a commit that referenced this issue Oct 16, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment