Features restricted to secure contexts - Web security 编辑
This reference lists the web platform features available only in secure contexts — see Secure Contexts for a definition and more details.
Current features available only in secure contexts
This section lists all the APIs available only in secure contexts, along with browser versions the limitation was introduced in, as appropriate.
Note: Only the browsers that actually support secure contexts are listed in this document. See here for information on secure contexts support.
| API | Chrome/Opera | Edge | Safari | Firefox |
|---|---|---|---|---|
| Async Clipboard API | 66 | Not supported | Not supported | 63 |
Background Sync (see SyncManager, for example) | 49 | Not supported | Not supported | Not supported |
Cache-Control: immutable | Not supported | 15 | 11 | 49 |
| Credential Management API | 51 | Not supported | Not supported | Not supported |
| Generic Sensor API | 67 | Not supported | Not supported | Not supported |
| Payment Request API (and Basic Card Payment). | 61 | 15 | 11.1 | In development (behind the dom.payments.request.enabled pref). |
| Push API | 42 | 17 | Not supported | 44 |
| Reporting API | Supported | Not supported | Not supported | Behind flag since Fx 65 |
| Service Workers | 40 | 17 | 11.1 | 44 |
| Storage API | 55 | Not supported | Not supported | 51 |
| Web Authentication API | 65 | In preview (17) | In development | 60 |
| Web Bluetooth | 56 | Not supported | Not supported | Not supported |
Web MIDI (see MIDIAccess, for example) | 43 | Not supported | Not supported | Not supported |
| Web Crypto API | 60 | 79 | Not supported | 75 |
Secure context restrictions that vary by browser
Some browsers may decide to disable certain APIs in non-secure contexts or apply other restrictions/security measures, despite the spec not requiring them. This section lists any such differences existing in browsers.
| API | Chrome | Edge | Safari | Firefox |
|---|---|---|---|---|
| Application Cache | Restricted to secure contexts from Chrome 70 (complete removal planned for Chrome 90). | Restricted to secure contexts from Edge 79 (removal planned for Edge 90). | public interest on deprecation WebKit bug 182442 | Restricted to secure contexts in Firefox 62 (complete removal from Firefox 84). |
Geolocation | Restricted to secure contexts in 50 | Restricted to secure contexts in 10 | Restricted to secure contexts in 55 | |
| Device Orientation / Device Motion | Deprecation warning | Deprecation warnings since 60. Note that these apply to secure contexts as well. | ||
| Encrypted Media Extensions | Restricted to secure contexts in 58 | Planned. | ||
| getUserMedia() | Restricted to secure contexts in Chrome 47 | Temporary access available only (users cannot choose "Remember this decision" in the permission request dialog). Restricted to secure contexts in Firefox 68. | ||
| Notifications | Restricted to secure contexts in Chrome 62 | Restricted to secure contexts in Firefox 67. | ||
| <a ping> attribute | Disabled in non-secure contexts | Support has been added since Firefox 3, but never been enabled by default (behind the browser.send_pings pref). | ||
| Presentation | Deprecation warning in 61 | |||
| Web Crypto API | Has been restricted to HTTPS since early days (API was visible in HTTP as well but operations failed). Restricted to secure contexts in Chrome 60 (API is no longer visible on non-secure contexts). | Restricted to secure contexts from Edge 79 | Restricted to secure contexts in Firefox 75 | |
| registerProtocolHandler() | Restricted to secure contexts in Firefox 62. |
See also
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论