Skip to content
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

Merged
merged 3 commits into from
May 18, 2016
Merged

Add "only-if-cached" cache mode back #295

merged 3 commits into from
May 18, 2016

Conversation

annevk
Copy link
Member

@annevk annevk commented May 4, 2016

Fixes #159. The difference with the previous attempt is that it now has
a “same-origin” mode restriction (enforced through the Fetch API).

@annevk
Copy link
Member Author

annevk commented May 4, 2016

@ehsan @tyoshino @mnot FYI (and if you'd like to review, please).

@ehsan
Copy link

ehsan commented May 12, 2016

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fetch uses

@mnot
Copy link
Member

mnot commented May 12, 2016

what about the privacy aspect (cache probing)?

@annevk
Copy link
Member Author

annevk commented May 13, 2016

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).
@mnot
Copy link
Member

mnot commented May 17, 2016

LGTM

@annevk annevk merged commit fef8c9a into master May 18, 2016
@annevk annevk deleted the only-if-cached branch May 18, 2016 15:19
@annevk
Copy link
Member Author

annevk commented May 18, 2016

Thanks!

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

Successfully merging this pull request may close these issues.

3 participants