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.