-
Notifications
You must be signed in to change notification settings - Fork 42
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
Don't require Cache API to have a secure context #165
Comments
The confusion for Firefox is probably due to the interfaces being exposed but throwing; https://bugzilla.mozilla.org/show_bug.cgi?id=1112134 covers attempts to change the interfaces to not be exposed when they're not supported, but there have been complications as a lot of tests break. From Firefox/Gecko's perspective, if IndexedDB was introduced today it would require SecureContext. Aside: I assume it's accidental this issue is filed against background-fetch? |
@asutherland Re:
I'm don't know you, so I'm confused: Are you actually speaking on behalf of Firefox/Gecko ? I don't know why it's against background-fetch - I searched for an issue with the same subject, found none, and created an issue. Let me add a couple other notes, for background:
[EDIT] [EDIT 2] [EDIT 3] |
Should this issue be either closed or moved to service worker spec? |
Agreed. This is unrelated to background fetch. |
It seems to only require a secure context due to being bundled with Service Workers, but Service Workers are not required for the cache API to be used or have utility. Firefox does not require them to have a secure context, and the discrepancy results in a note on the MDN page (https://developer.mozilla.org/en-US/docs/Web/API/CacheStorage) and a bug report to Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=1026063) which in turn points back to the spec.
Splitting the cache API into it's own spec (#879) would remove the conceptual bundling and reflect the fact that the cache API doesn't need Service Workers.
Further, indexedDB does not require a secure context and has it's own spec (https://w3c.github.io/IndexedDB/) so treating Cache API similarly makes sense.
The text was updated successfully, but these errors were encountered: