-
Notifications
You must be signed in to change notification settings - Fork 346
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
Add "only-if-cached" cache mode back #295
Conversation
LGTM! |
the response. | ||
|
||
<dt>"<code title="">only-if-cached</code>" | ||
<dd>Fetches uses any response in the HTTP cache matching the request, not paying attention to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fetch uses
what about the privacy aspect (cache probing)? |
Cache probing would only be possible same-origin since this feature is restricted to same-origin. It might make it slightly easier if there was an XSS exploit to figure out capability URLs perhaps, but that still seems rather hard and with an XSS exploit you likely have access to sensitive information anyway. |
Fixes #159. The difference with the previous attempt is that it now has a “same-origin” mode restriction (enforced through the Fetch API).
LGTM |
Thanks! |
Fixes #159. The difference with the previous attempt is that it now has
a “same-origin” mode restriction (enforced through the Fetch API).