Feature-Policy: geolocation
Feature-Policy: geolocation
The HTTP Feature-Policy header geolocation directive controls whether the current document is allowed to use the Geolocation Interface. When this policy is enabled, calls to getCurrentPosition() and watchPosition() will cause those functions' callbacks to be invoked with a GeolocationPositionError code of PERMISSION_DENIED.
By default, the Geolocation API can be used within top-level documents and their same-origin child frames. This directive allows or prevents cross-origin frames from accessing geolocation. This includes same-origin frames.
Syntax
-
<allowlist>
-
A list of origins for which the feature is allowed. See Feature-Policy.
Default policy
Default allow list for geolocation is 'self'.
General example
SecureCorp Inc. wants to disable the Geolocation API within all browsing contexts except for its own origin and those whose origin is https://example.com. It can do so by delivering the following HTTP response header to define a feature policy:
With an <iframe> element
FastCorp Inc. wants to disable geolocation for all cross-origin child frames, except for a specific <iframe>. It can do so by delivering the following HTTP response header to define a feature policy:
Then include an allow attribute on the <iframe> element:
<iframe src="https://other.com/map" allow="geolocation"></iframe>
Interestingly, allow attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.
Specifications
Browser compatibility
|
Desktop |
Mobile |
|
Chrome |
Edge |
Firefox |
Internet Explorer |
Opera |
Safari |
WebView Android |
Chrome Android |
Firefox for Android |
Opera Android |
Safari on IOS |
Samsung Internet |
geolocation |
60
|
79
|
74
Only supported through the allow attribute on <iframe> elements.
|
No
|
47
|
No
|
60
|
60
|
79
Only supported through the allow attribute on <iframe> elements.
|
44
|
No
|
8.0
|